1. Preface
The Text Encoding Initiative (TEI) has developed over 20 years into a key technology in text-centric humanities disciplines, with an extremely wide range of applications, from diplomatic editions to dictionaries, from prosopography to speech transcription and linguistic analysis. It has been able to achieve its range of use by adopting a descriptive rather than prescriptive approach , by recommending customization to suit particular projects, and by eschewing any attempt to dictate how the digital texts should be rendered or exchanged. However, this flexibility has come at the cost of relatively limited success in interoperability. In our view there is a distinct set of uses (primarily in the area of digitized ‘European’-style books) that would benefit from a prescriptive recipe for digital text; this will sit alongside other domain-specific, constrained TEI customizations, such as the very successful Epidoc in the epigraphic community. TEI Simple may become a prototype for a new family of constrained customizations. For instance, a TEI Simple MS for manuscript based work could be built on top of the ENRICH project, drawing on many of the lessons and some of the code for TEI Simple.
The TEI has long maintained an introductory subset (TEI Lite), and a constrained customization for use in outsourcing production to commercial vendors (TEI Tite), but both of these permit enormous variation, and have nothing to say about processing. The TEI Simple project can be viewed in some ways as a revision of TEI Lite. Leaving aside elements for the <teiHeader>, TEI Lite and TEI Simple are customization of approximately the same scope, choosing respectively 91 and 105 out of the 552 TEI elements and sharing 80 of them. TEI Simple targets the area of Letters in the broad and old-fashioned sense of that term. Its choice of elements reflects the practices followed in the encoding of large-scale archives, notably the archives produced by the Text Creation Partnership, but also the German Text Archive and a variety of archives encoded according to Level 4 of the Best Practices for TEI in Libraries. It is simple only with regard to its <text> element. The <teiHeader> follows the same rules as TEI-All.
TEI Simple focuses on interoperability, machine generation, and low-cost integration. In earlier discussions this project was called "TEI Nudge" because it was offered in the spirit of Richard Thaler's and Cass Sunstein's Nudge with its persuasive argument that in many walks of life people will make better choices if they are offered well-designed default solutions, as long as they are free to opt out of them. The TEI architecture facilitates customizations of many kinds; TEI Simple aims to produce a complete ‘out of the box’ customization which meets the needs of the many users for whom the task of creating a customization is daunting or seems irrelevant. TEI Simple in no way intends to constrain the expressive liberty of encoders who do not think that it is either possible or desirable to follow this path. It does, however, promise to make life easier for those who think there is some virtue in travelling that path as far as it will take you, which for quite a few projects will be far enough. Some users will never feel the need to move beyond it, others will outgrow it, and when they do they will have learned enough to do so.
The most distinctive feature of TEI Simple is a ‘cradle to grave’ processing model that associates the TEI Simple schema with explicit and standardized options for displaying and querying texts. This means being able to specify what a programmer should do with particular TEI elements when they are encountered, allowing programmers to build stylesheets that work for everybody and to query a corpus of documents reliably.
The modal case of a TEI project is a scholarly edition of some text that originated in a print or manuscript world. The edition may start from the fresh transcription of a source or it may start from the existing encoding of a text, e.g. a text from the EEBO TCP archive. Such projects call on a combination of skills that are not often found in the same person. The scholars care about the accuracy of the transcription and relevance of the encoding to their purpose and that of other users. If you have editorial responsibility for a TEI encoded text, you must know enough about TEI elements and practices to do this well. You need not know much about or be interested in the often very complex procedures required to turn the encoded text into something that users can work with. On the other hand the programmers and designers are very familiar with those procedures, but they may not have the time or inclination to become familiar with the intricacies of TEI encoding.
The processing model offers a bridge across that divide. The aim is to lower the access barriers to working with TEI-encoded texts in various web environments. Programmers familiar with a particular web environment, whether Django, Drupal, eXist, Ruby on Rails, or others will be able to integrate TEI Simple-based projects into their environment with moderate effort and with no more than their usual tools and skills. Scholars or other individuals who primarily care about getting the encoding right need not concern themselves with subsequent stages. If they can do their encoding within the limits of TEI Simple, they can be confident that the fruits of their en-coding are available to users. Users, in turn, can have greater confidence that the query poten-tial of encoded texts is in fact made available to them through appropriate query routines. This is conspicuously not the case with most TEI-encoded texts now: it is very difficult to write or train a search engine if you cannot make reasonably stable assumptions about the structure of the documents to be queried.
This introduction to TEI Simple consists of three parts. They address different audiences and make different assumptions about what the reader is likely to know. The first of these addresses readers who know little or nothing about XML and can safely be skipped by readers who are familiar with it. The second is a tour of the elements in TEI Simple from an encoder's perspective. This section is a revision of the excellent introduction to TEI Lite by Lou Burnard and Michael Sperberg-McQueen. It follows that document wherever it can while adding this or deleting that. The third part is a short tour of the Processing Model and is written for programmers who are familiar with Web technologies but new to TEI.
2. A very gentle introduction to XML and TEI
2.1. Hierarchies and Metaphors in XML
The best full-scale introduction to the technologies that undergird TEI is found in Lou Buranrd's "Gentle Introduction to XML in Chapter 5 of the TEI:P5 Guidelines. " If you come from a History, Literature, or Philosophy department and have never worked with XML you may not find it quite so gentle, especially in its later chapters. This chapter addresses you and tries to lay out some basic facts about XML and TEI in language that stays as close to layman's language as possible. Examples are chosen from TEI Simple, but their point is to demonstrate general aspects of XML. Consult the "Tour of TEI Simple" for a detailed discussion of elements and their rules. The is some overlap in the discussions. If you are a novice, the repetition may be helpful. If you are an expert, you want to skip this section altogether.
A word of advice before proceeding any further. It is possible to use simple text editing software to work with XML, but if you value your time do not even think about doing it. Use an XML editor instead. An XML editor is a piece of software that "knows about" the general features of XML and the particular features of a distinct XML language such as TEI. It can save you countless hours by discovering (or even preventing) the many logical and typographical errors that are easy to make and hard to fix. Some XML editors are freeware. The software that will save you the most time is likely not to be free. There are several excellent XML editors. In the TEI world, oXygen is probably the most widely used.
XML stands for Extensible Markup Language. It is a set of rules for creating hierarchical data structures or Ordered Hierarchies of Content Objects (OHCO). You are familiar with such structures from the hard drive of your computer. It is a single container or "root" directory, which you can subdivide into an arbitrary number of subdirectories, each of which is "recursively" divisible into arbitrarily many subdirectories. Within the limits of the size of your hard drive each container is infinitely variable in size and adjusts to stuff that that you add or subtract.
The technical terms of XML make extensive use of tree and family metaphors. In XML parlance the root of a tree is envisaged as a single cell. In visualizations the tree is typically inverted so that the tree grows downwards from a root in the sky. Each branching of such a tree is called a node, and a node with no further branches is often called a leaf node. A good XML editor lets you present the outline or tree structure of your document in the form of a navigation panel.
As for the family metaphor, there is no sex in XML, and reproduction proceeds by parthenogenesis. A parent may have an indefinite number of child elements, but a child element has only one parent. It may have many ancestors, but at any level of the hierarchy there is only one of them. It is a defining feature of such hierarchical structures that for any node there is one and only path from the root to any node, or from any node to any other node. In XML the technical term for that path is XPath, which is both a name for such a path and a quite complicated computer language for getting from any "here" to any "there".
On your hard drive a container is known as a directory or folder. In an XML document, containers are known as elements. Container suggests volume and a three-dimensional structure, but the content of elements is text, which unfolds in a single temporal direction, envisaged from left to right in many, but by no means all, languages.
The resemblances between your hard drive and an XML document in it are closer than you may think. XQuery is the name of a computer language that handles XML documents. In that language
declare variable $collection := collection('/Users/martin/dropbox/speechdirectory'); is a way of saying Follow the Xpath that starts from the top container and follow it through its branchings (expressed by the solidus or forward slash) until you come to the container called "speechdirectory." Call it "collection" and identify it as an object on which further operations can be performed.
The dollar sign identifies a variable and its name. "speechdirectory" happens to be a directory on my computer with TEI documents that have a lot of speeches in them. Now consider the following piece of code: for $title in $collection//filesDesc/titleStmt/title return $titleThis is a for statement used in many computer languages. It loops through a set of files, in this case all the files defined as the variable $collection. For each of these files it follows any path that leads via the elements <fileDesc> and <titleStmt> to the element <title>. It gives to that element the variable name $title and returns, i.e. produces as the result of its operation, the variable $title. The result is a long list with entries like the following.
<title>A dialogue between Sir R.L. Knight, and T.O.D</title>
<title>A new dialogue between some body and no body, or, The Observator observed</title>
The XQuery chained together the hard drive's filepath and all the XPaths in the $collection variable that lead to <title> children of <titleStmt> elements. You might say that the root element of the XML document becomes a child element of your drive.Why is the piece of code frame with a black border while its output is displayed in green field and with a green border? Anything that appears in green is a valid TEI XML fragment if it appears in the right context. Code framed in black makes no such claim.
As this example demonstrates, it takes a fair amount of prose to describe a very simple operation. Just about any individual operation with XML is quite simple, but there are a lot of them and they nest. Some of the most distinctive features and difficulties of XML are highlighted if you envisage the hierarchical structure as as one-dimensional stream. Imagine an XML document as a pair of parentheses with parentheses and nested parentheses within it. Nesting is a simple concept, but it is not easy for human minds or eyes to follow a nested structure beyond the third level. An interesting technical term in this regard is serialize. You don't need to know (I certainly don't) just how the data of an XML document are stored in the innards of a computer. But when they are produced by the machine for you in a manner that you can make sense of they are serialized. This serialization appears typically on the two dimensional space of a page, where the single text stream is broken into familiar lines. The typographical line has been a remarkably stable structure for millennia, with limits imposed by the capacities of the human eye. But it is helpful to remember that a line is a convenient construct of a longer discursive linear stream.
The parentheses that mark the boundaries of XML elements are more complicated things than round, square, or curly brackets. They are constructs enclosed in angle brackets, are known as tags, and have names. The opening tag of an element with the name "someElement" looks like <someElement>, while the closing tag adds a solidus after the left angle brackets:</someElement>. As with a directory on your computer, you can put as much stuff between those tags as your hard drive will hold. The following is a well-formed XML document
<someELement>Mary had a little lamb</someELement>
But so is
<someELement> In the beginning God created the heaven and the earth....The grace of our Lord Jesus Christ be with you all. Amen.</someELement>
with all the other words of the Bible in between.
2.2. Well-formed XML
The term well-formed has a very specific meaning in XML. An XML text must be well-formed, and it may be valid. For an XML document to be well-formed it only needs to meet the conditions that must be true of all XML documents. There are not many of them, but the two most important are that a) the document must be enclosed by a root element, and b) that the name of an element must be spelled exactly the same way in the opening and closing tag. Thus
<someElement>Mary had a little lamb</someelement>
is not a well-formed XML document, because XML is case-sensitive and the spelling of the closing tag "someelement" does not match the spelling of the opening tag "someElement." Neither is
<line>Mary had a little lamb</line>
<line>Its fleece was white as snow</line>
But
<linegroup>
<line>Mary had a little lamb</line>
<line>Its fleece was white as snow</line>
</linegroup>
is well-formed XML because the two <line> elements are enclosed by the root element <linegroup> and the opening and closing tag names are spelled the same way.
These simple examples of well-formed XML consist of element wrappers that enclose text. From a reader's perspective XML has slightly awkward ways of referring to ‘just text’. The software that processes an XML text is known as a parser, a term borrowed from traditional grammar. Just as you parse a sentence by determining where its different parts begin and end, so an XML parser goes through an XML file and inspects its parts. It looks for opening and closing tags of each element as well as the stuff enclosed by them, which consists either of other elements or of PCDATA or parsed character data, stuff that the XML Parser after examination has recognized as proper text.
Except for the left angle bracket (<) and the ampersand (&) any Unicode character can show up in PCDATA. Because the XML parser uses (<) to identify the beginning of an element tag, it cannot be used directly in plain text or PCDATA. Instead you use a character entity to represent them. A character entity is a periphrastic expression that is wrapped in an opening ampersand and a closing semicolon. Since there are no words that begin with the former and end with the latter they act as an unambiguous marker that their content refers to and retrieves something special, whether a single character or all of Hamlet. The character entity for the left angle bracket is (<), where ‘lt’ stands for ‘less than’ to reflect the common use of that character in mathematical notation.
Because the ampersand is used as the opening symbol for a character entity, it also must be escaped and cannot be used directly. Its character entity is "ampersand + amp + semicolon" (&). These character entities are two of five predefined entities in the XML specifications that you can use without formally declaring them. The other three are the apostrophe ('), the double quotation mark ("), and the "greater-than" symbol or right angle bracket (>). Of these, the apostrophe entity is useful if you want to distinguish between the uses of the same character as the genitive marker and a single quotation mark.
Within the range of TEI Simple you probably will not need to know any more about character entities, but you can find out more about them at XML Entity Definitions for Characters (2nd Edition).
2.3. Valid XML
The requirement that everything in a well-formed XML document must be enclosed by a root element does not take you very far. A well-formed directory structure on a hard drive can be, and often is, a complete mess. XML becomes interesting and useful only when it is valid. XML has rules for making rules that specify for any element
- what elements it may or must contain or be contained by
- how often it may appear in its parent elemtn
- in what order it may or must appear
A set of such rules is known as a schema. You can use these rules about rules to make up your own schema, but if you want to share your documents and make sure that others can use them you are better off using a schema that has been designed by others for general use in some domain, whether Chemistry, Mathematics, or whatever. TEI is such a schema, and its purpose is to facilitate the encoding of documents that fall under the category of Letters very broadly defined.
How does a machine know that a document is an XML document,whether with or without a schema? Any XML document must begin with one or more processing instructions that tell the machine what to do with it. The minimal processing instruction simply says ‘I am an XML document’ and does so with the line
<?xml version="1.0" encoding="UTF-8"?>
at the top of the file. The statement ‘I am a TEI Simple document’ is a more elaborate affair:
<?xml-model href="http://raw.githubusercontent.com/TEIC/TEI-Simple/master/teisimple.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://raw.githubusercontent.com/TEIC/TEI-Simple/master/teisimple.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
You can encode quite successfully in TEI Simple by just cutting and pasting this code. If you work with a program like oXygen, you can choose a new document as a TEI Simple document, and it will open with all the required processing instructions. It is, however, useful to hava rough idea of what is going on here. A processing instruction comes in a <? ...?> wrapper, which answers to the machine's question ‘What shall I do here?’ In our example there are two instructions. The first one says
Follow the instructions in the schema teisimple.rng. which you will find at the URL "http://raw.githubusercontent.com/TEIC/TEI-Simple/master/teisimple.rng".
The second instruction, which is rather more cryptic, specifies that the rules for the <teiHeader> element differ from the rules for the <text> element.
A schema is a very technical document and can be expressed in various schema languages. In the TEI world Relax NG is the most popular schema language. You can mostly treat the TEI Simple schema (or any other schema) as a black box whose operations you trust. Until about a dozen years, working with XML texts was a painful exercise. XML texts are equally unforgiving when it comes to orthographic or logical errors. Both are very easy to make and very hard to find or fix in a document of any complexity. Modern editing software wil validate your document as you work on it. That is to say, it will read your document and check whether it complies with the rules declared in the schema. If it discovers an error, it will tell you about the what and where of that error right then and there. It is a good investment of your time to learn how to read such error messages.
Although working with XML is much less painful than it used to, you still have to understand the particular rules that are formulated in the arcane language of the schema. You also need to know something about the rule-making rules of XML in order to work with TEI documents. And it helps to remind yourself constantly of some basic facts about XML. An XML document is in principle human-readable. If the only surviving copies of Dante's Inferno, Cervantes' Don Quixote, or Shakespeare's Hamlet were XML versions they could be read by humans who know Italian, Spanish, or English. But an XML document is not made to be read by a human. It is made to be processed by a machine for some purpose, whether displaying it on a screen, printing it out in some formating, or retrieving bits of information from it. An XML document is to a considerable extent agnostic about the purposes to which it may be put. It is not a single purpose version of its source. In particular, it is not designed as a reader-friendly document, although you may generate a reader-friendly version from it.
2.4. XML as a declarative markup language
Like any other XML language, TEI is a declarative markup language. If in a printed book you come across the sentence ‘Julius Caesar was assassinated on March 15, 44 BCE’ and you see the string "Julius Caesar" in italics you may reasonably infer that the type setting program followed an "imperative" procedure that said something like ‘when you come to J start printing in italics and stop when you've done 'r'’. Word processors work that way. In TEI that sentence might be encoded as
<s>
<name>Julius Caesar</name> was assassinated on <date>March 15, 44 BCE</date>
</s>
This encoding has no imperatives, but is a sequence of declarations where These declarations include no instructions about what to do with them. They do allow a machine to retrieve the content of all elements that have the tags <name>, <date> or <s>. If the sentence came from an Early Modern document in which names are frequently italicized, the encoding might go like
<s>
<name rendition="#italics">Julius Caesar</name> was assassinated on <date>March 15, 44 BCE</date>
</s>
The attribute rendition in this case declares that in the source document the name was italicized, but the encoding does not tell you what to do with that fact. What is true of this sentence is true of every TEI text. It is a set of declarations rather than a set of instructions.2.5. The Nature of XML rules
TEI is a specific markup language designed to encode texts that originated in a print or manuscript world. You can also use it to generate born digital documents, but you will understand its quirks more readily if you keep its original purpose in mind. The XML rules for specifying the TEI markup language have to do with
- what elements may contain or are contained by other elements
- the order of child elements within a particular parent element
- the number of child elements that a parent element may contain
The words may, must and may not are important technical terms that the machine can understand when it validates an encoding. There is also the ocasional should, but should is not a term the machine can make sense of. It involves conventions that it is helpful to observe, even though for one reason or another they cannot be expressed in terms of may, must or may not.
2.6. A simple example of the rules
The skeleton of a TEI document provides a good example for the ways in which the rule-making capabilities of XML are exercised. A TEI document MUST have one and only one root element, and it name is TEI. The element name TEI is a specific feature of the TEI schema. The requirement for a root element is a requirement of well-formed XML.
The TEI root element MUST have two child elements, <teiHeader> and <text>. There MUST be only one of each, and <teiHeader> MUST come before <text>. These are TEI specific rules, but they observe the rule-making rules of XML.
<teiHeader> and <text> relate to each other as a catalogue record to the item it catalogues. <teiHeader> consists of data about <text> or metadata.
Encoding the header is a very different thing from encoding the text, and information from the header is never included in a representation of the text. We will leave the header alone, except for noting briefly what MUST be in it. Here is an example of a minimal header:
<teiHeader>
<fileDesc>
<titleStmt>
<title>My next book</title>
</titleStmt>
<publicationStmt>
<p>not yet published</p>
</publicationStmt>
<sourceDesc>
<p>original document</p>
</sourceDesc>
</fileDesc>
</teiHeader>
The header MUST have a <fileDesc> element or file description, which answers at least the following three questions:
- What is my name? (<titleStmt>)
- Who published me? (<pubStmt>)
- Where do I come from? (<sourceDesc>)
The <fileDesc> element MAY have a lot of other child elements, but it MUST have <titleStmt>, <pubStmt>, <sourceDesc>, only one of each and in that order. This is a very simple example of XML rules codifying practices from some domain, here the world of published books. The normal case of a TEI document represents a file that has been digitized and published from a printed source. But this hypothetical example represents a digital file that has not been published and was born digital.
In this simple example, <titleStmt>,<pubStmt>,and <sourceDesc> do not have text content, but their child elements <p> and <title> do. Some elements can only contain other elements, some elements can contain mixed content, i.e. text nodes and child elements. Some elements typically contain only text nodes, but TEI Simple has no element that MUST contain only a text node.
If you work with TEI mainly as an encoder, mixed content is an easy concept to get used to. If you are in the business of processing encoded text it is the cause of many problems. Consider our earlier example:
<s>
<name rendition="#italics">Julius Caesar</name> was assassinated on <date>March 15, 44 BCE</date>.
</s>
For the machine this simple sentence exists as three separate text nodes that are children of different elements. A lot of thought has gone into writing software that will easily extract these different text nodes and combine them into a single utterance.So much for the header, at least for now. Let us turn to <text>, the container for encoding the actual document, including its title page if it has one. A book is a bibliographical unit, which may contain one or more work(s). The second quarto of Hamlet is a book with one work. The Shakespeare Folio of 1623 contains three dozen separate works. While the TEI can handle both situations, we will focus here on the normal case of ‘one book, one work’, but it is useful to acknowledge the fact that the relationship between book and work and be very complex and raises tricky encoding questions.
The <text> element MUST contain one and only one <body> element. It MAY contain a<front> or <back> element, or both of them, but only one of each. <front> MUST precede and <back> MUST follow <body>. This is another example of perfectly obvious and sensible rules from some domain being codified in the rigid rules of the XML schema. Since you are very unlikely to encode the sequence <back>, <front>, <body>, you will not benefit from the validator's telling you that this is not valid XML, but there are many other and less obvious cases where the validator is helpful.
The <body> element MUST have something in it. It will be happy with a single paragraph, as in
<body>
<p>This is all I have to say</p>
</body>
but you are more likely to find more elaborate structures, such as <body>
<div>
<head>Chapter One</head>
<p>It was a dark and stormy night</p>
</div>
<div>
<head>Chapter Two</head>
<p>more stuff about the weather...</p>
</div>
</body>
The chapter or section level <div> element is one of the TEI workhorses. You MAY have as many of them as you like in your <front> <body> or <back> elements, and you MAY nest them as deeply as you like.
The paragraph level <p> element is the other workhorse of the TEI. Any element that MAY contain <p> elements MAY contain any number of them. Unlike <div> elements, <p> MAY contain plain text or PCDATA (and typically will consist mostly of it), but a <p> element MAY NOT nest within another <p> element. This is a perfectly sensible rule. The <p> element is based on the model of the paragraph. Paragraphs divide into sentences; you don't expect them to divide into sub-paragraphs. Or, if there is a document with paragraphs and sub-paragraphs, you are probably in the world of lists and list items. The TEI has elements for lists and their items, and a list item MAY have a <list> child element. But even though <p> MAY NOT be a child of <p>, it is possible that a valid child of <p> could have a valid child element <p>. Whether you SHOULD use such encoding is another question.
It is useful to think of most TEI elements as operating mainly at one of three levels:
- Text structure elements elements articulate the macrostructure of your document, e.g. <front>,<body>,<back>,<div>. With some very specialized exceptions, such elements MAY NOT contain PCDATA.
- Block elements, principally <p> and <l> contain stretches of plain text whose end is almost universally marked by a line break in print.
- Inline elements operate at the microstructure of discourse. Printed text will often use italics or some other device to highlight a word or phrase. It is often, but not always possible to determine the reason. In TEI the <hi> element is the all-purpose element to encode inline words or phrases that have been highlighted.
But wherever one draws a line, there are phenomena that want to cross that line. In TEI there are several inter elements that can occur within paragraphs (inline) or between paragraphs (block). The most common of these is the versatile and slippery <q> element. Paragraphs often end with a quotation in a pattern like the following:
<p>.....and wrote as follows:
<q>
<p>one paragraph</p>
<p>another paragraph</p>
<p>yet another paragraph</p>
</q>
</p>
The fact that the paragraph does not end with a period but with a colon might lead you to think of the quotation as part of the previous paragraph. It does, however, lead to a deeply nested structure in which <p> elements are the descendants of <p> elements. If you like #5 of the Zen of Python (‘flat is better than nested’) you might decide that the paragraph is terminated by the colon and that <q> should be the right sibling rather than child of <p>:
<p>.....and wrote as follows:</p>
<q>
<p>one paragraph</p>
<p>another paragraph</p>
<p>yet another paragraph</p>
</q>
That is a very different case from a quotation of two lines of verse in the middle of a sentence, as in
<p>.....when Hamlet says:
<q>
<l>But that the dread of something after death,</l>
<l>The undiscovered country from whose bourn</l>
<l>No traveller returns, puzzles the will</l>
</q>
he means that...</p>
In the latter case there is no ambiguity or choice, and there is nothing strained about <l> as a descendant of <p> In the former case, there is ambiguity, and you may want to choose the option that avoids strained nesting. With nested structures it is useful to follow the advice ‘as much as necessary but as little as possible’.
2.7. About Namespaces
Namespaces are a little like surnames, letting you distinguish between Miller, Henry and Smith, Henry. For instance, HTML and TEI both use elements with the names <p> and <div>. But these are "false friends" with very different meanings and operating rules. By convention a namespace takes the form of a URL. The full name of an element is known as its "qualified name" or QName, and in one conventional notation it is written by prefixing the element name with the namespace in curly braces Thus the namespace of TEI is http://www.tei-c.org/ns/1.0, and the full name of a TEI element such as <p> is {http://www.tei-c.org/ns/1.0}p.
Because QNames are very clumsy things to manipulate, shortcuts have been invented. If you map the namespace to a prefix, tei:p will stand for {http://www.tei-c.org/ns/1.0}p, five instead of thirty characters. The choice of the prefix is arbitrary, but the prefix and element name must be connected by a colon. Unless you manipulate an XML text with XSLT, xquery, or some other language, you don't have to worry much about namespaces. But it is useful to know about them. If you do have to use them remember that they are fussy and a common source of error.
2.8. About Attributes
Elements can have attributes. The term is borrowed from grammar, and attributes relate to elements pretty much as adjectives relate to nouns. An attribute consists of a key-value pair, such as type='act', where the term before the equal sign is the name of the attribute and the term after the equal sign is the value. The value must be in quotation marks,whether single or double, but smart quotation marks will raise an error message. Thus <div typ="act" n=3"> would be a way of specifying a particular <div> as containing "Act III" of some play.
In well-formed XML, there are rules about the names of attributes, but no rules about what attributes to use with what elements or what values to associate with the attributes. In valid XML, the rules for attributes are specified in the schema. There are rules about what attributes may be used with with what elements and what kinds of data may, must, or may not appear in attribute values. In the TEI schema some attributes are global and can be used in the same manner for any element. Other attributes are specific to a particular set of elements.
A few of the global attributes in the TEI schema belong to the xml namespace. The two that you are likely to encounter often are xml:id and xml:lang. The former specifies an ID for an element that is unique within the document. The latter specifies the language in which the document (or part of it) is written. The rules for these two attributes are not TEI specific but follow the general rules for XML. That is why instead of id and lang these attributes always appear with their XML prefix xml:id and xml:lang.
In the TEI schema the value of an xml:id attribute must be a proper XML Name: it must begin with an alphabetic character; it may include digits, periods, hyphens, and underscores, but not commas, or semicolons. Because the colon required to link a namespace prefix to an attribute name you should only use it for that purpose. TEI has its own rules for what values may, may not, or must appear in different attributes.
The two most widely used global attributes in TEI are n and rendition. The name of the former is short for "number," and numbering of one kind or another is its most common, but not its only use. There are hardly any restrictions on what you can use for its attribute values. You can even, while you are working with a document, embed comments, as long as you remember to remove them in time. If n="5" is a proper value, so is n="5 check this again later." But you will be better off using the formal commenting protocol of XML, wrapping any kind of comment in <!-- [my comment] -->
Other attributes values are much fussier. The <l> supports a part attributed with a fixed list of values Y, N, I, M, F for yes, no, initial, medial, and final. The value for the target attributes for the linking element <ref> may consist of one or more URL's separated by white space.
The type attribute, which is available for some but not all elements, is a very powerful device for making more granular distinctions among kinds of discourse, especially when it is combined with a controlled vocabulary. For instance, the TEI schema include a <lg> element for encoding any kind of grouping of lines of verse. A controlled vocabulary for tagging stanzaic and metrical patterns is a great device for enhancing the query potential of a corpus of poems.
2.9. Limitations of TEI as an XML Markup Language
As an XML markup language TEI is committed to two axioms:
- A document is an OHCO or ordered hierarchy of content objects
- The presentation of a document can be neatly separated from its structure
Both of these axioms are deeply problematical when it comes to texts, but they are true often enough to be useful. Many texts divide neatly into single hierarchical structures, but others do not, and rhetorical effects frequently rely on the reader's or listener's effortless management of what in TEI parlance is called overlapping or concurrent hierarchies. Take the last two lines of Hamlet's soliloquy:
The fair Ophelia! Nymph, in thy orisonsBe all my sins remembered.
The prosodic structure of two lines of blank verse is counterpointed by a syntactic structure in which a sentence begins in the middle of one line and spills over without a break into the next line. You might be tempted to encode this as follows
<quote>
<l>
<s>The fair Ophelia!</s> <s>Nymph, in thy orisons</l>
<l> Be all my sins remembered.</s></l>
</quote>
But this will generate the error message ‘The element type "s" must be terminated by the matching end-tag "s". ’ It is a cardinal rule of XML that no child element may have two parents. There are various workarounds. You can use milestones, as in
<quote>
<l>
<milestone unit="sentence"/>.The fair Ophelia!
<milestone unit="sentence"/> Nymph, in thy orisons</l>
<l> Be all my sins remembered.</l>
</quote>
Using the punctuation element <pc> you would get a similar articulation: <quote>
<l>The fair Ophelia<pc unit="sentence">!</pc>
<milestone unit="sentence"/> Nymph, in thy orisons</l>
<l> Be all my sins remembered<pc unit="sentence">.</pc>
</l>
</quote>
You could also use the next and previous attributes to tie the two <s> elements together: <quote>
<l>The fair Ophelia!
<s xml:id="s1" next="#s2">Nymph, in thy orisons</s>
</l>
<l>
<s xml:id="s2" previous="#s1">Be all my sins remembered.</s>
</l>
</quote>
These workarounds do a more or less adequate job at articulating a secondary structure in the face of a dominant structure, but they are workarounds. There are other and more powerful workarounds. Chapter 18 of the Guidelines discusses feature structures, and there is stand-off markup, where different forms of textual segmentation and annotation are kept in separate documents that point to individual tokens or token ranges in the text. Feature structures take you well beyond TEI Simple, and stand-off will also be most beyond its range.The second axiom, that content is entirely separable from presentation, will rub most literary critics the wrong way. If you are used to reading a book printed in Fraktur you may feel that printing it in Antiqua robs it of its spirit. In Vergil's Eclogues up or down things happen at oddly regular intervals. Vergil appears to have written these poems on page blocks with forty lines and knew when he was writing at the top of page (nice words about Maecenas) or at the bottom (bad things happening to bad guys). There are countless examples of playing with layout and typography, from George Herbert to concrete poetry.
If you make the physical layout of a text the organizing structure you can do that by using the <surface > element and its children. That is also beyond the scope of TEI Simple, but it is fully documented in Chapter 11 of the Guidelines
TEI is about text, and texts are written in natural languages. Natural Language Processing (NLP) is a very important part of computing. If you engage in it you will discover early on that human language is highly rule-bound, that you can write procedures that will allow a machine to capture many of these rules very accurately and at great speed, but there is always an algorithmically intractable residue. St. Jerome, the translator of the Bible into Latin, spoke of ‘ipsum... suum et, ut ita dicam, vernaculum linguae genus’ (the distinct and as it were vernacular nature of each language) and the 16th-century French poet Du Bellay argued that literal translation destroys the ‘je ne scay quoy’ of a language. Pope wrote of a ‘grace beyond the reach of art’. Text encoding is a way of enabling a machine to process texts in ways that help human readers "make sense" of them. The machine can take you quite far, but it will only take you so far. In an encoding project of any complexity there will always be some moments when you remember this line from Wallace Stevens' Connoisseurs of Chaos:
The squirming facts exceed the squamous mind.
2.10. Should, Should Not, and Tag Abuse
Valid encoding is not necessarily good encoding, just as rigid compliance with the law does not always square with justice. Here we are in the realm of Aristotle's epieikia or equity as a principle that complements rigid compliance with a set of rules. The word lives in a space tenuously circumscribed by the probable, the reasonable, and the appropriate--very much like the space of the French twins vraisemblance and bienséanceWhat SHOULD you do when confronted with a problem to which the schema offers no obvious solution? Do as your neighbours do is good advice when you live in a good neighbourhood, and as a TEI encoder you happen to live in a very friendly and helpful neighbourhood. Sign up for the TEI listserv and ask for advice. It will come to you from just about any continent, very promptly at any hour of the day or night, and it is nearly always relevant. Following the TEI list and pondering its advice is the best way of getting a feel for the discretionary space surrounds all rulles, and it will keep you from committing tag abuse, the TEI community's term for encoding practices that are valid but make no sense or worse.
3. A tour of TEI Simple from an encoding perspective
3.1. A Short Example
We begin with a short example, intended to show what happens when a passage of prose is typed into a computer by someone with little sense of the query potential of a digitally encoded text. In an ideal world, such output might be generated by a very accurate optical scanner. It attempts to be faithful to the appearance of the printed text, by retaining the original line breaks, by introducing blanks to represent the layout of the original headings and page breaks, and so forth. Where characters not available on the keyboard are needed (such as the accented letter a in faàl or the long dash), it attempts to mimic their appearance.
CHAPTER 38
READER, I married him. A quiet wedding we had: he and I, the par-
son and clerk, were alone present. When we got back from church, I
went into the kitchen of the manor-house, where Mary was cooking
the dinner, and John cleaning the knives, and I said --
'Mary, I have been married to Mr Rochester this morning.' The
housekeeper and her husband were of that decent, phlegmatic
order of people, to whom one may at any time safely communicate a
remarkable piece of news without incurring the danger of having
one's ears pierced by some shrill ejaculation and subsequently stunned
by a torrent of wordy wonderment. Mary did look up, and she did
stare at me; the ladle with which she was basting a pair of chickens
roasting at the fire, did for some three minutes hang suspended in air,
and for the same space of time John's knives also had rest from the
polishing process; but Mary, bending again over the roast, said only --
'Have you, miss? Well, for sure!'
A short time after she pursued, 'I seed you go out with the master,
but I didn't know you were gone to church to be wed'; and she
basted away. John, when I turned to him, was grinning from ear to
ear.
'I telled Mary how it would be,' he said: 'I knew what Mr Ed-
ward' (John was an old servant, and had known his master when he
was the cadet of the house, therefore he often gave him his Christian
name) -- 'I knew what Mr Edward would do; and I was certain he
would not wait long either: and he's done right, for aught I know. I
wish you joy, miss!' and he politely pulled his forelock.
'Thank you, John. Mr Rochester told me to give you and Mary
this.'
I put into his hand a five-pound note. Without waiting to hear
more, I left the kitchen. In passing the door of that sanctum some time
after, I caught the words --
'She'll happen do better for him nor ony o' t' grand ladies.' And
again, 'If she ben't one o' th' handsomest, she's noan faa\l, and varry
good-natured; and i' his een she's fair beautiful, onybody may see
that.'
I wrote to Moor House and to Cambridge immediately, to say what
I had done: fully explaining also why I had thus acted. Diana and
474
JANE EYRE 475
Mary approved the step unreservedly. Diana announced that she
would just give me time to get over the honeymoon, and then she
would come and see me.
'She had better not wait till then, Jane,' said Mr Rochester, when I
read her letter to him; 'if she does, she will be too late, for our honey-
moon will shine our life long: its beams will only fade over your
grave or mine.'
How St John received the news I don't know: he never answered
the letter in which I communicated it: yet six months after he wrote
to me, without, however, mentioning Mr Rochester's name or allud-
ing to my marriage. His letter was then calm, and though very serious,
kind. He has maintained a regular, though not very frequent correspond-
ence ever since: he hopes I am happy, and trusts I am not of those who
live without God in the world, and only mind earthly things.
This transcription suffers from a number of shortcomings:
- the page numbers and running titles are intermingled with the text in a way which makes it difficult for software to disentangle them;
- no distinction is made between single quotation marks and apostrophe, so it is difficult to know exactly which passages are in direct speech;
- the preservation of the copy text's hyphenation means that simple-minded search programs will not find the broken words;
- the accented letter in faàl and the long dash have been rendered by ad hoc keying conventions which follow no standard pattern and will be processed correctly only if the transcriber remembers to mention them in the documentation;
- paragraph divisions are marked only by the use of white space, and hard carriage returns have been introduced at the end of each line. Consequently, if the size of type used to print the text changes, reformatting will be problematic.
We now present the same passage, as it might be encoded in TEI Simple. As we shall see, there are many ways in which this encoding could be extended, but as a minimum, the TEI approach allows us to represent the following distinctions:
- Paragraph and chapter divisions are now marked explicitly.
- Apostrophes are distinguished from quotation marks; direct speech is explicitly marked.
- The accented letter and the long dash are correctly represented.
- Page divisions have been marked with an empty <pb/> element alone.
- The lineation of the original has not been retained and words broken by typographic accident at the end of a line have been re-assembled without comment.
- For convenience of proof reading, a new line has been introduced at the start of each paragraph, but the indentation is removed.
<pb n="474"/>
<div type="chapter" n="38">
<p>Reader, I married him. A quiet wedding we had: he and I, the parson and clerk, were alone
present. When we got back from church, I went into the kitchen of the manor-house, where
Mary was cooking the dinner, and John cleaning the knives, and I said —</p>
<p>
<q>Mary, I have been married to Mr Rochester this morning.</q> The housekeeper and her
husband were of that decent, phlegmatic order of people, to whom one may at any time safely
communicate a remarkable piece of news without incurring the danger of having one's ears
pierced by some shrill ejaculation and subsequently stunned by a torrent of wordy
wonderment. Mary did look up, and she did stare at me; the ladle with which she was basting
a pair of chickens roasting at the fire, did for some three minutes hang suspended in air,
and for the same space of time John's knives also had rest from the polishing process; but
Mary, bending again over the roast, said only —</p>
<p>
<q>Have you, miss? Well, for sure!</q>
</p>
<p>A short time after she pursued, <q>I seed you go out with the master, but I didn't know
you were gone to church to be wed</q>; and she basted away. John, when I turned to him, was
grinning from ear to ear. <q>I telled Mary how it would be,</q> he said: <q>I knew what Mr
Edward</q> (John was an old servant, and had known his master when he was the cadet of the
house, therefore he often gave him his Christian name) — <q>I knew what Mr Edward would do;
and I was certain he would not wait long either: and he's done right, for aught I know. I
wish you joy, miss!</q> and he politely pulled his forelock.</p>
<p>
<q>Thank you, John. Mr Rochester told me to give you and Mary this.</q>
</p>
<p>I put into his hand a five-pound note. Without waiting to hear more, I left the kitchen.
In passing the door of that sanctum some time after, I caught the words —</p>
<p>
<q>She'll happen do better for him nor ony o' t' grand ladies.</q> And again, <q>If she
ben't one o' th' handsomest, she's noan faàl, and varry good-natured; and i' his een she's
fair beautiful, onybody may see that.</q>
</p>
<p>I wrote to Moor House and to Cambridge immediately, to say what I had done: fully
explaining also why I had thus acted. Diana and <pb n="475"/> Mary approved the step
unreservedly. Diana announced that she would just give me time to get over the honeymoon,
and then she would come and see me.</p>
<p>
<q>She had better not wait till then, Jane,</q> said Mr Rochester, when I read her letter
to him; <q>if she does, she will be too late, for our honeymoon will shine our life long:
its beams will only fade over your grave or mine.</q>
</p>
<p>How St John received the news I don't know: he never answered the letter in which I
communicated it: yet six months after he wrote to me, without, however, mentioning Mr
Rochester's name or alluding to my marriage. His letter was then calm, and though very
serious, kind. He has maintained a regular, though not very frequent correspondence ever
since: he hopes I am happy, and trusts I am not of those who live without God in the world,
and only mind earthly things.</p>
</div>
This particular encoding represents a set of choices or priorities. As a trivial example, note that in the second example, end-of-line hyphenation has been silently removed. Conceivably Brontë (or her printer) intended the word ‘honeymoon’ to appear as ‘honey-moon’ on its second appearance, though this seems unlikely: our decision to focus on Brontë's text, rather than on the printing of it in this particular edition, makes it impossible to be certain. This is an instance of the fundamental selectivity of any encoding. An encoding makes explicit only those textual features of importance to the encoder. It is not difficult to think of ways in which the encoding of even this short passage might readily be extended. For example:
- a regularized form of the passages in dialect could be provided;
- footnotes glossing or commenting on any passage could be added;
- pointers linking parts of this text to others could be added;
- proper names of various kinds could be distinguished from the surrounding text;
- names could be classified as personal, geographical, or institutional
- detailed bibliographic information about the text's provenance and context could be prefixed to it;
- a linguistic analysis of the passage into sentences, clauses, words, etc., could be provided, each unit being associated with appropriate category codes;
- the text could be segmented into narrative or discourse units;
- systematic analysis or interpretation of the text could be included in the encoding, with potentially complex alignment or linkage between the text and the analysis, or between the text and one or more translations of it;
- passages in the text could be linked to images or sound held on other media.
TEI-recommended ways of carrying out most of these are described in the remainder of this document. Consult the full Guidelines for more detail.
3.2. The Structure of a TEI Text
Almost all TEI-conformant texts contain (a) a TEI header (marked up as a <teiHeader> element) and (b) the transcription of the text proper (marked up as a <text> element). These two elements are combined together to form a single <TEI> element, which must be declared within the TEI namespace. The full name of the <TEI> element is < xmlns="http://www.tei-c.org/ns/1.0"> .
The header is described in more detail in section 3.17. The Electronic Title Page. The word "almost" in the paragraph above acknowledges the existence of a form of TEI encoding that seeks to capture what is often called the materiality of the text. Some of the relevant element names , <facsimile>, <surface>, <zone>, give you a sense of this approach, where the content of element would be images or other media types rather than transcribed text. While this set of elements is outside the scope of TEI Simple, digital representations that combine transcription with facsimiles are likely to be more common in the future. The global facs attribute is the obvious device for linking pages or other chunks of transcribed TEI Simple text to facsimiles. For more information consult the section on Digital Facsimiles in the Guidelines.
A TEI text may be unitary (a single work) or composite (a collection of single works, such as an anthology). In either case, the text may have an optional front or back. In between is the body of the text, which, in the case of a composite text, may consist of groups, each containing more groups or texts.
A unitary text will be encoded using an overall structure like this:
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<!-- [ TEI Header information ] -->
</teiHeader>
<text>
<front>
<!-- [ front matter ... ] -->
</front>
<body>
<!-- [ body of text ... ] -->
</body>
<back>
<!-- [ back matter ... ] -->
</back>
</text>
</TEI>
Note that in the example above the text between "<!--" and "-->" is a comment that is ignored by the XML parser. You can use the same convention for interspersing comments in your XML document, and it will be similarly ignored. Why then does it show up in the example? Everything in the example is wrapped in a special <egXML> element, which lets you display "raw" XML fragments without the XML parser acting on them.
In the remainder of this document, we discuss chiefly simple text structures, but composite texts are briefly discussed in 3.15. In each of the following sections we begin with a short list of relevant TEI elements and give their formal definition, followed by definitions for any attributes specific to that element. These references are linked to full specifications for each object, as given in the TEI Guidelines. In most cases, short examples are also given.
For example, here are the elements discussed so far:
- TEI (TEI document) contains a single TEI-conformant document, containing a single TEI header, a single text, one or more members of the model.resourceLike class, or a combination of these. A series of <TEI> elements may be combined together to form a <teiCorpus> element.
- teiHeader (TEI header) supplies the descriptive and declarative information making up an electronic title page for every TEI-conformant document.
- text contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample.
- teiCorpus contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more TEI elements, each containing a single text header and a text.
3.3. Encoding the Body
As indicated above, a simple TEI document at the textual level consists of the following elements:
- front (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body.
- group contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc.
- body (text body) contains the whole body of a single unitary text, excluding any front or back matter.
- back (back matter) contains any appendixes, etc. following the main part of a text.
Elements specific to front and back matter are described below in section 3.16. Front and Back Matter. In this section we discuss the elements making up the body of a text.
3.3.1. Text Division Elements
The body of a prose text may be just a series of paragraphs, or these paragraphs may be grouped together into chapters, sections, subsections, etc. Each paragraph is tagged using the <p> tag. The <div> element is used to represent any such grouping of paragraphs.
- p (paragraph) marks paragraphs in prose.
- div (text division) contains a subdivision of the front, body, or back of a text.
The type attribute on the <div> element may be used to supply a conventional name for this category of text division, or otherwise distinguish them. Typical values might be ‘book’, ‘chapter’, ‘section’, ‘part’, ‘poem’, ‘song’, etc. For a given project, it will usually be advisable to define and adhere to a specific list of such values.
A <div> element may itself contain further, nested, <div>s, thus mimicking the traditional structure of a book, which can be decomposed hierarchically into units such as parts, containing chapters, containing sections, and so on. TEI texts in general conform to this simple hierarchic model.
The xml:id attribute may be used to supply a unique identifier for the division, which may be used for cross references or other links to it, such as a commentary, as further discussed in section 3.7. Cross References and Links. It is often useful to provide an xml:id attribute for every major structural unit in a text, and to derive its values in some systematic way, for example by appending a section number to a short code for the title of the work in question, as in the examples below. It is particularly useful to supply such identifiers if the resource concerned is to be made available over the web, since they make it much easier for other web-based applications to link directly to the corresponding parts of your text.
The n attribute may be used to supply (additionally or alternatively) a short mnemonic name or number for a division, or any other element. If a conventional form of reference or abbreviation for the parts of a work already exists (such as the book/chapter/verse pattern of Biblical citations), the n attribute is the place to record it; unlike the identifier supplied by xml:id, it does not need to be unique.
The xml:lang attribute may be used to specify the language of the division. Languages are identified by an internationally defined code, as further discussed in section 3.5.3. Foreign Words or Expressions below.
The rendition attribute may be used to supply information about the rendition (appearance) of a division, or any other element, as further discussed in section 3.5. Marking Highlighted Phrases below. You should document your use of the possible values of rendition in the taggin declaration (<tagsDecl> of your header.
These four attributes, xml:id, n, xml:lang, and rend are so widely useful that they are allowed on any element in any TEI schema: they are global attributes. Other global attributes defined in the TEI Simple schema are discussed in section 3.7.3. Special kinds of Linking.
The value of every xml:id attribute should be unique within a document or across a corpus, if your project spans many texts.. One simple way of ensuring that this is so is to make it reflect the hierarchic structure of the document. For example, Smith's Wealth of Nations as first published consists of five books, each of which is divided into chapters, while some chapters are further subdivided into parts. We might define xml:id values for this structure as follows:
<body>
<div xml:id="WN1" n="I" type="book">
<div xml:id="WN101" n="I.1" type="chapter">
<!-- ... -->
</div>
<div xml:id="WN102" n="I.2" type="chapter">
<!-- ... -->
</div>
<!-- ... -->
<div xml:id="WN110" n="I.10"
type="chapter">
<div xml:id="WN1101" n="I.10.1"
type="part">
<!-- ... -->
</div>
<div xml:id="WN1102" n="I.10.2"
type="part">
<!-- ... -->
</div>
</div>
<!-- ... -->
</div>
<div xml:id="WN2" n="II" type="book">
<!-- ... -->
</div>
</body>
A different numbering scheme may be used for xml:id and n attributes: this is often useful where a canonical reference scheme is used which does not tally with the structure of the work. For example, in a novel divided into books each containing chapters, where the chapters are numbered sequentially through the whole work, rather than within each book, one might use a scheme such as the following:
<body>
<div xml:id="TS01" n="1" type="volume">
<div xml:id="TS011" n="1" type="chapter">
<!-- ... -->
</div>
<div xml:id="TS012" n="2" type="chapter">
<!-- ... -->
</div>
</div>
<div xml:id="TS02" n="2" type="volume">
<div xml:id="TS021" n="3" type="chapter">
<!-- ... -->
</div>
<div xml:id="TS022" n="4" type="chapter">
<!-- ... -->
</div>
</div>
</body>
Here the work has two volumes, each containing two chapters. The chapters are numbered conventionally 1 to 4, but the xml:id values specified allow them to be regarded additionally as if they were numbered 1.1, 1.2, 2.1, 2.2.3.3.2. Headings and Closings
Every <div> may have a title or heading at its start, and (less commonly) a trailer such as ‘End of Chapter 1’ at its end. The following elements may be used to transcribe them:
- head (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc.
- trailer contains a closing title or footer appearing at the end of a division of a text.
Some other elements which may be necessary at the beginning or ending of text divisions are discussed below in section 3.16.1.2. Prefatory Matter.
Whether or not headings and trailers are included in a transcription is a matter for the individual transcriber to decide. Where a heading is completely regular (for example ‘Chapter 1’) or may be automatically constructed from attribute values (e.g.
<div type="chapter" n="1">), it may be omitted; where it contains otherwise unrecoverable text it should always be included. For example, the start of Hardy's Under the Greenwood Tree might be encoded as follows: <div xml:id="UGT1" n="Winter" type="Part">
<div xml:id="UGT11" n="1" type="Chapter">
<head>Mellstock-Lane</head>
<p>To dwellers in a wood almost every species of tree ... </p>
</div>
</div>
3.3.3. Prose, Verse and Drama
As in the Bronte example above, the paragraphs making up a textual division are tagged with the <p> tag. In poetic or dramatic texts different tags are needed, to represent verse lines and stanzas in the first case, or individual speeches and stage directions in the second. :
- l (verse line) contains a single, possibly incomplete, line of verse.
- lg (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc.
- sp (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text.
- speaker contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment.
- stage (stage direction) contains any kind of stage direction within a dramatic text or fragment.
Here, for example, is the start of a poetic text in which verse lines and stanzas are tagged:
<lg n="I">
<l>I Sing the progresse of a
deathlesse soule,</l>
<l>Whom Fate, with God made, but doth not controule,</l>
<l>Plac'd in
most shapes; all times before the law</l>
<l>Yoak'd us, and when, and since, in this I
sing.</l>
<l>And the great world to his aged evening;</l>
<l>From infant morne, through manly
noone I draw.</l>
<l>What the gold Chaldee, of silver Persian saw,</l>
<l>Greeke brass, or
Roman iron, is in this one;</l>
<l>A worke t'out weare Seths pillars, bricke and
stone,</l>
<l>And (holy writs excepted) made to yeeld to none,</l>
</lg>
Note that the <l> element marks verse lines, not typographic lines: the original lineation of the first few lines above has not therefore been made explicit by this encoding, and may be lost. The <lb/> element described in section 3.4. Page and Line Numbers might additionally be used to mark typographic lines if so desired.
Here is the end of a famous dramatic text, in which speeches and stage directions are marked:
<sp>
<speaker>Vladimir</speaker>
<p>Pull on your trousers.</p>
</sp>
<sp>
<speaker>Estragon</speaker>
<p>You want me to pull off my trousers?</p>
</sp>
<sp>
<speaker>Vladimir</speaker>
<p>Pull <emph>on</emph> your trousers.</p>
</sp>
<sp>
<speaker>Vladimir</speaker>
<p>
<stage>(realizing his trousers are down)</stage>.
True</p>
</sp>
<stage>He pulls up his trousers</stage>
<sp>
<speaker>Vladimir</speaker>
<p>Well? Shall we go?</p>
</sp>
<sp>
<speaker>Estragon</speaker>
<p>Yes, let's go.</p>
</sp>
<stage>They do not move.</stage>
Note that the <stage> (stage direction) element can appear either within a speech or between speeches. The <sp> ("speech") element contains, following an optional <speaker> element indicating who is speaking, either paragraphs (if the speech is in prose) or verse lines or stanzas as in the next example. In this case, it is quite common to find that verse lines are split between speakers. The easiest way of encoding this is to use the part attribute to indicate that the lines so fragmented are incomplete :
<div type="Act" n="I">
<head>ACT I</head>
<div type="Scene" n="1">
<head>SCENE I</head>
<stage rendition="#italic"> Enter Barnardo and Francisco, two Sentinels, at several doors</stage>
<sp>
<speaker>Barn</speaker>
<l part="Y">Who's there?</l>
</sp>
<sp>
<speaker>Fran</speaker>
<l>Nay, answer me. Stand and unfold yourself.</l>
</sp>
<sp>
<speaker>Barn</speaker>
<l part="I">Long live the King!</l>
</sp>
<sp>
<speaker>Fran</speaker>
<l part="M">Barnardo?</l>
</sp>
<sp>
<speaker>Barn</speaker>
<l part="F">He.</l>
</sp>
<sp>
<speaker>Fran</speaker>
<l>You come most carefully upon your hour.</l>
</sp>
<!-- ... -->
</div>
</div>
The same mechanism may be applied to stanzas which are divided between two speakers:
<div>
<sp>
<speaker>First voice</speaker>
<lg type="stanza" part="I">
<l>But why drives on that ship so fast</l>
<l>Withouten wave or wind?</l>
</lg>
</sp>
<sp>
<speaker>Second Voice</speaker>
<lg part="F">
<l>The air is cut away before.</l>
<l>And closes from behind.</l>
</lg>
</sp>
<!-- ... -->
</div>
The <sp> element can also be used for dialogue presented in a prose work as if it were drama, as in the next example, which also demonstrates the use of the who attribute to bear a code identifying the speaker of the piece of dialogue concerned:
<div>
<sp who="#OPI">
<speaker>The reverend Doctor Opimian</speaker>
<p>I do not think I have named a single unpresentable fish.</p>
</sp>
<sp who="#GRM">
<speaker>Mr Gryll</speaker>
<p>Bream, Doctor: there is not much to be said for bream.</p>
</sp>
<sp who="#OPI">
<speaker>The Reverend Doctor Opimian</speaker>
<p>On the contrary, sir, I think there is much to be said for him. In the first
place....</p>
<p>Fish, Miss Gryll -- I could discourse to you on fish by the hour: but for the present I
will forbear.</p>
</sp>
</div>
Here the who attribute values (#OPI etc.) are links, pointing to a list of the characters in the novel, each of which has an identifier: <list>
<head>Characters in the novel</head>
<item xml:id="OPI">
<name>Dr Opimian</name> : named for the famous Roman fine wine</item>
<item xml:id="GRM">
<name>Mr Gryll</name> : named for the mythical Gryllus, one of Ulysses'
sailors transformed by Circe into a pig, who argues that he was happier in that state than
as a man</item>
</list>
3.4. Page and Line Numbers
Page and line breaks etc. may be marked with the following elements.
- pb/ (page break) marks the start of a new page in a paginated document.
- lb/ (line break) marks the start of a new (typographic) line in some edition or version of a text.
- milestone/ marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element.
The <pb/> and <lb/> elements are special cases of the general class of milestone elements which mark reference points within a text. The generic <milestone/> element can mark any kind of reference point: for example, a column break, the start of a new kind of section not otherwise tagged, or in general any significant change in the text not marked by an XML element. Milestone elements have no content; whatever they have to say is contained in their attributes, most frequently a <unit> attribute in combination with an n attribute. Their "empty" status is marked by the fact that their opening and closing tags are collapsed into one: the notation <milestone/> is a shortcut for <milestone></milestone>.
The <lb/> and <pb/> elements are shortcuts or syntactic sugar for
<milestone unit="line"/>
or <milestone unit="page"/>
When working from a paginated original, it is often useful to record its pagination, if only to simplify later proof-reading. It is also useful for aligning an encoded text with a set of page images. The facs attribute helps with this alignment, which is not always straightforward. The numbering schemes of the printed pages and their image may, but often do not, correspond. The Text Creation Partnership transcriptions of Early English Books Online texts are a good example. The transcriptions were based on digital scans of double page microfilm images. Each double page image has an image number, which does not correspond to the page number, not to speak of the many printed pages that have no page numbers to begin with. Consider the following three examples:
<pb facs="page8" n="14"/>
<pb facs="page8" n="15"/>
<pb facs="page8"/>
In the first two examples, you have the printed page numbers for a double page image. The third example refers to a page image whose pages have no printed numbers. The value of the facs attribute could also be a complete URL to the site where the images are located, but if its first and longer part has been recorded once in the metadata, the simple image number will be sufficient to construct a link.The placement of <pb/> elements relative to their surrounding elements is a tricky matter of SHOULD. While TEI schema does not restrict their placement, it is recommended that milestone elements for lines, pages, or whatever should mark their beginning. Consider the case of a poem where two lines are split across different pages. All of the following encodings are valid TEI:
<l>Mary had a little lamb</l>
<pb n="13" facs="7"/>
<l>Its fleece was white as snow</l>
<l>Mary had a little lamb</l>
<l>
<pb n="13" facs="7"/>Its fleece was white as snow
</l>
<l>Mary had a little lamb<pb n="13" facs="7"/>
</l>
<l>Its fleece was white as snow</l>
While the third example is valid, it breaks the rule that you should put milestones at the beginning. The first and second examples observe that rule, but the first example is preferable on logical, aesthetic and practical grounds. The new page begins with the line rather than the first word in the line.The placement of the milestone before the line makes processing a little easier. It is also a little easier to read, and while XML documents are not created for readers, they are in principle readable, and greater readability is a marginal benefit.Line breaks in prose are for the most part typographical accidents, and many encoders will rightly think of them as not worth their attention. But sometimes you do want to make the transcription mirror the physical layout of the written word on the page. This is especially true of manuscripts where the precise alignment of image and transcription makes things easier for the reader.
Digital transcriptions produced with optical character recognition (OCR) create special opportunities and challenges. They mimic the boundaries of characters, words, and lines on the page, and from their "whitespace XML" you can algorithmically infer much structural encoding, although the algorithmic constructs will always need some manual tweaking. OCR texts also require careful proofreading. This work will clearly benefit from the line-by-line correspondence of page image and transcription.
End-of-line (EOL) hyphens are a vexing problem for which there is no good solution. For many purposes it may be good enough to get rid of them tacitly. Given
I am not per-
suaded that EOL hyphens are worth keeping.
you can turn this into
I am not persuaded that EOL hyphens are worth keeping.
If you want to mark the line breaks of the printed source you could remove the EOL hyphen and keep the word on the line where it began, as in
I am not persuaded
<lb/> that EOL hyphens are worth keepingThis is a perfectly acceptable solution, and few readers will object to it, especially if you document your practice in the relevant section of the header. The downside of both solutions is that you may accidentally delete what you think is an EOL hyphen when if fact it is a real hyphen. There are ways of protecting yourself against such an error. Check if that word occurs with a hyphen in line-medial position. If it does not, you are probably safe. In the unlikely event that it occurs in line-medial position both with and without a hyphen you would not know which it is in the line-terminal position. But relax: there is textual authority for whichever way you jump.
Recording the presence of an EOL hyphen in a completely unambiguous manner turns out to be surprisingly difficult. First, while there are several Unicode characters that look like a hyphen, there is none that unambiguously declares: ‘I am an EOL hyphen’. You can do something like
I am not per-<lb/>suaded that EOL hyphens are worth keeping.
That leaves the status of your hyphen ambiguous but then it was ambiguous in the source as well. This solution (or other variants of it) makes it a little more difficult for the machine to figure out that 'per' and 'suaded' are a single token. In a cost benefit analysis you have to figure out whether the additional processing cost is worth the gain of typographical detail.Note:
If features such as pagination or lineation are marked for more than one edition, specify the edition in question using the ed attribute, and supply as many tags are necessary. For example, in the following passage we indicate where the page breaks occur in two different editions (ED1 and ED2)
<p>I wrote to Moor House and to Cambridge immediately, to say what I had done: fully
explaining also why I had thus acted. Diana and <pb ed="ED1" n="475"/> Mary approved the step
unreservedly. Diana announced that she would <pb ed="ED2" n="485"/>just give me time to get
over the honeymoon, and then she would come and see me.</p>
3.5. Marking Highlighted Phrases
3.5.1. Changes of Typeface, etc.
Highlighted words or phrases are those made visibly different from the rest of the text, typically by a change of type font, handwriting style, ink colour etc., which is intended to draw the reader's attention to some associated change.
The global rendition attribute can be attached to any element, and used wherever necessary to specify details of the highlighting used for it in the source. For example, a heading rendered in bold might be tagged <head rendition="#bold">, and one in italic <head rendition="#italic">.
The values to be used for the rendition attribute are not specified by the TEI Guidelines, since they will depend entirely on the needs of the particular project. Some typical values might include italic, bold etc. for font variations; center, right etc. for alignment; large, small etc. for size; smallcaps, allcaps etc. for type variants and so on.
It is not always possible or desirable to interpret the reasons for such changes of rendering in a text. In such cases, the element <hi> may be used to mark a sequence of highlighted text without making any claim as to its status.
- hi (highlighted) marks a word or phrase as graphically distinct from the surrounding text, for reasons concerning which no claim is made.
In the following example, the use of a distinct typeface for the subheading and for the included name are recorded but not interpreted:
<p>
<hi rendition="#gothic">And this Indenture further
witnesseth</hi> that the said <hi rendition="#italic">Walter Shandy</hi>, merchant, in
consideration of the said intended marriage ...
</p>
Alternatively, where the cause for the highlighting can be identified with confidence, a number of other, more specific, elements are available.
- foreign identifies a word or phrase as belonging to some language other than that of the surrounding text.
- label contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.
- title contains a title for any kind of work.
Some features (notably quotations {titles, and foreign words) may be found in a text either marked by highlighting, or with quotation marks. In either case, the element <q> (as discussed in the following section) should be used. If the highlighting is to be recorded, use the global rendition attribute.
As an example of the elements defined here, consider the following sentence: On the one hand the Nibelungenlied is associated with the new rise of romance of twelfth-century France, the romans d'antiquité, the romances of Chrétien de Troyes, and the German adaptations of these works by Heinrich van Veldeke, Hartmann von Aue, and Wolfram von Eschenbach. Interpreting the role of the highlighting, the sentence might look like this:
<p>On the one hand the <title>Nibelungenlied</title>
is associated with the new rise of romance of twelfth-century France, the <foreign>romans
d'antiquité</foreign>, the romances of Chrétien de Troyes, ...</p>
Describing only the appearance of the original, it might look like this: <p>On the one hand the <hi rendition="#italic">Nibelungenlied</hi> is associated with the new rise of romance of twelfth-century France,
the <hi rendition="#italic">romans d'antiquité</hi>, the romances of Chrétien de Troyes,
...</p>
3.5.2. Quotations and Related Features
Like changes of typeface, quotation marks are conventionally used to denote several different features within a text, of which the most frequent is quotation. When possible, we recommend that the underlying feature be tagged, rather than the simple fact that quotation marks appear in the text, using the following elements:
- q (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used.
- quote (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text.
Here is a simple example of a quotation:
<p>Few dictionary makers are likely to forget Dr. Johnson's description of the
lexicographer as <q>a harmless drudge.</q>
</p>
To record how a quotation was printed (for example, in-line or set off as a display or block quotation), the rendition attribute should be used. This may also be used to indicate the kind of quotation marks used.
Direct speech interrupted by a narrator can be represented simply by ending the quotation and beginning it again after the interruption, as in the following example:
<p>
<q>Who-e debel you?</q> — he at last said —
<q>you no speak-e, damme, I kill-e.</q> And so saying, the lighted tomahawk began
flourishing about me in the dark.
</p>
If it is important to convey the idea that the two <q> elements together make up a single speech, the linking attributes next and prev may be used, as described in section 3.7.3. Special kinds of Linking.Quotations may be accompanied by a reference to the source or speaker, using the who attribute, whether or not this is explicit in the text, as in the following example:
<q who="#Wilson">Spaulding, he came
down into the office just this day eight weeks with this very paper in his hand, and he
says:—<q who="#Spaulding">I wish to the Lord, Mr. Wilson, that I was a red-headed
man.</q>
</q>
This example also demonstrates how quotations may be embedded within other quotations: one speaker (Wilson) quotes another speaker (Spaulding).The creator of the electronic text must decide whether quotation marks are replaced by the tags or whether the tags are added and the quotation marks kept. If the quotation marks are removed from the text, the rend attribute may be used to record the way in which they were rendered in the copy text.
3.5.3. Foreign Words or Expressions
Words phrases, or longer stretches of test that are not in the main language of the texts may be tagged as such in one of two ways. The global xml:lang attribute may be attached to any element to show that it uses some other language than that of the surrounding text. Where there is no applicable element, the element <foreign> may be used, again using the xml:lang attribute. For example:
<p>John has real <foreign xml:lang="fr">savoir-faire</foreign>.</p>
<p>Have you read <title xml:lang="de">Die
Dreigroschenoper</title>?</p>
<div xml:lang="la">{75 pages of Latin}</div>
As these examples show, the <foreign> element should not be used to tag foreign words if some other more specific element such as <title>, or <div> applies.
The codes used to identify languages, supplied on the xml:lang attribute, must be constructed in a particular way, and must conform to common Internet standards1, as further explained in the relevant section of the TEI Guidelines. Some simple example codes for a few languages are given here:
| zh | Chinese | grc | Ancient Greek |
| en | English | el | Greek |
| enm | Middle English | ja | Japanese |
| fr | French | la | Latin |
| de | German | sa | Sanskrit |
3.6. Notes
A note is any additional comment found in a text, marked in some way as being out of the main textual stream. It is a special and very common form of linking, because a note always targets some part of the text, whether implicitly or explicitly. All notes should be marked using the same tag, note, whether they appear as block notes in the main text area, at the foot of the page, at the end of the chapter or volume, in the margin, or in some other place:
- note contains a note or annotation.
Notes may be in a different hand or typeface, may be authorial or editorial, and may have been added later. Use type and resp attributes to distinguish between different kinds of notes or identify their authors.
A note is typically linked to a point of attachment that is represented by a siglum such as an alphanumerical or other character, typically in superscripted form. When encoding such a text, it is conventional to replace this siglum by the content of the annotation, duly marked up with a note element. This may not always be possible for example with marginal notes, which may not be anchored to an exact location. For ease of processing, it may be adequate to position marginal notes before the relevant paragraph or other element.
An alternative method takes a "belt and suspenders" approach towards making sure that the relationship of a <note> element to its point of attachment is always spelled out explicitly. In the following example, the source text marks the point of attachment with a superscripted "7". A failsafe way of encoding this may take the following form:
<p>...some text <ref xml:id="r7" target="n7"
rendition="#superscript">7</ref>
<note xml:id="n7" n="7">a note about some text</note>
</p>
This is a rather verbose representation of a simple note marker in a printed text. But it can usually be generated via a script, and it ensures that there is no uncertainty about the relationship between a <ref> element in a stable location and a <note> element whose physical location is a variable thing, whether in its original form, its encoding, or its display in some output of that encoding. With this notation it no longer matters whether you encode your notes in inline or in standoff manner, that is to say, keep them next to their place of attachment or in a separate place.If the note lacks an explicit point of attachment in the text, which is often the case with marginal notes, you can use the pointer element <ptr>, which differs from <ref> in being empty.
Marginal notes often are subject to different interpretations about their status. They are very common in Early Modern printed books, recede over the course of the 18th century, but are still an integral feature of Gibbon's Decline and Fall of the Roman Empire. Many marginal notes are like footnotes, endnotes, or inline citations. A marginal note will very often provide the reference to an inline Biblical quotation. But some text in the margins is quite different in structure or purpose from notes that happen to be printed in the margin. In some Early Modern plays stage directions are routinely printed in the margin.
<stage place="margin"> would be the appropriate way of tagging them. Quite often the text in the margins operates more more like a summary or heading than a reference or explanatory note. In such cases <label place="margin"> may be the most appropriate tag, but the boundary between heading and annotation may be blurry, as in the following case: <lg xml:id="RAM609">
<note place="margin">The
curse is finally expiated</note>
<l>And now this spell was snapt: once more</l>
<l>I viewed the ocean green,</l>
<l>And looked far forth, yet little saw</l>
<l>Of what had else been seen
—</l>
</lg>
It is tempting to think of text in the margins as being notes by definition. On the other hand, if you ask yourself whether text in the margins provides additional information or is more like an abstract of what is to come, it may be quite easy to distinguish between <note> and <label> in most cases. As for stage directions in the margin, think of <stage> as syntactic sugar for <note type="stage">3.7. Cross References and Links
Explicit cross references or links from one point in a text to another in the same or another document may be encoded using the elements described in this section. Implicit links (such as the association between two parallel texts, or that between a text and its interpretation) may be encoded using the linking attributes discussed in section 3.7.3. Special kinds of Linking.
3.7.1. Simple Cross References
A cross reference from one point within a single document to another can be encoded by a tacit or explicit use of the <ref> element:
- ref (reference) defines a reference to another location, possibly modified by additional text or comment.
In the tacit use of the <ref> element you use it as as an empty element, simply marking a point from which a link is to be made, whereas in the explicit use the element may contain some text as well, typically identifying the target of the cross reference. You can use the element tacitly in a cross reference which is to be indicated by some non-verbal means such as a symbol or icon, or in an electronic text by a button. It is also useful in document production systems, where the formatter can generate the correct verbal form of the cross reference.
The following two forms, for example, are logically equivalent :
See especially <ref target="#SEC12">section 12 on
page 34</ref>.
See especially <ref target="#SEC12"/>.
The value of the target attribute on either element may be the identifier of some other element within the current document. The passage or phrase being pointed at must bear an identifier, and must therefore be tagged as an element of some kind. In the following example, the cross reference is to a <div> element: ... see especially <ref target="#SEC12"/>. ...
<div xml:id="SEC12">
<head>Concerning Identifiers</head>
<!-- ... -->
</div>
Because the xml:id attribute is global, any element in a TEI document may be pointed to in this way. In the following example, a paragraph has been given an identifier so that it may be pointed at:
... this is
discussed in <ref target="#pspec">the paragraph on links</ref> ...
<p xml:id="pspec">Links
may be made to any kind of element ...</p>
Sometimes the target of a cross reference does not correspond with any particular feature of a text, and so may not be tagged as an element of some kind. If the desired target is simply a point in the current document, the easiest way to mark it is by introducing an <anchor/> element at the appropriate spot. If the target is some sequence of words not otherwise tagged, the <seg> element may be introduced to mark them. These two elements are described as follows:
- anchor/ (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.
- seg (arbitrary segment) represents any segmentation of text below the ‘chunk’ level.
In the following (imaginary) example, <ref> elements have been used to represent points in this text which are to be linked in some way to other parts of it; in the first case to a point, and in the second, to a sequence of words:
Returning to <ref target="#ABCD">the point where I
dozed off</ref>, I noticed that <ref target="#EFGH">three words</ref> had been circled in
red by a previous reader
This encoding requires that elements with the specified identifiers (
ABCD and EFGH in this example) are to be found somewhere else in the current document. Assuming that no element already exists to carry these identifiers, the <anchor/> and <seg> elements may be used: ....
<anchor type="bookmark" xml:id="ABCD"/> .... ....<seg type="target" xml:id="EFGH"> ...
</seg> ...
The type attribute should be used (as above) to distinguish amongst different purposes for which these general purpose elements might be used in a text. Some other uses are discussed in section 3.7.3. Special kinds of Linking below.
3.7.2. Pointing to other documents
So far, we have shown how the <ref> element may be used for cross-references or links whose targets occur within the same document as their source. The element may also be used to refer to elements in any other XML document or resource, such as a document on the web, or a database component. This is possible because the value of the target attribute may be any valid universal resource indicator (URI)Note: A full definition of this term, defined by the W3C (the consortium which manages the development and maintenance of the World Wide Web), is beyond the scope of this tutorial: however, the most frequently encountered version of a URI is the familiar ‘URL’ used to indicate a web page, such as http://www.tei-c.org/index.xml.
A URI may reference a web page or just a part of one, for example http://www.tei-c.org/index.xml#SEC2. The hash sign indicates that what follows it is the identifier of an element to be located within the XML document identified by what precedes it: this example will therefore locate an element which has an xml:id attribute value of SEC2 within the document retrieved from http://www.tei-c.org/index.xml. In the examples we have discussed so far, the part to the left of the sharp sign has been omitted: this is understood to mean that the referenced element is to be located within the current document.
Parts of an XML document can be specified by means of other more sophisticated mechanisms using a special language called Xpath, also defined by the W3C. This is particularly useful where the elements to be linked to do not bear identifiers and must therefore be located by some other means. A full specification of the language is well beyond the scope of this document; here we provide only a flavour of its power.
In the XPath language, locations are defined as a series of steps, each one identifying some part of the document, often in terms of the locations identified by the previous step. For example, you would point to the third sentence of the second paragraph of chapter two by selecting chapter two in the first step, the second paragraph in the second step, and the third sentence in the last step. A step can be defined in terms of the document tree itself, using such concepts as parent, descendent, preceding, etc. or, more loosely, in terms of text patterns, word or character positions. This is not the document to describe in detail the powers of XPath. But unless you think of TEI encoding as just another form of typesetting—which emphatically is not its purpose—the decision to encode any part of a text this way rather than that way should always be guided by the sense that somebody at some time will want to decode or retrieve that part of the text for some purpose, about which you may not know very much at the point of encoding. XPath has been, and is likely to remain, the set of rules for decoding the encoded. A general understanding of what you can or cannot do with XPath is a useful thing to know in any encoding project.
3.7.3. Special kinds of Linking
The following special purpose linking attributes are defined for every element in the TEI Simple schema:
- ana
- links an element with its interpretation.
- corresp
- links an element with one or more other corresponding elements.
- next
- links an element to the next element in an aggregate.
- prev
- links an element to the previous element in an aggregate.
The ana (analysis) attribute is intended for use where a set of abstract analyses or interpretations have been defined somewhere within a document, as further discussed in section 3.14. Analysis. For example, a linguistic analysis of the sentence ‘John loves Nancy’ might be encoded as follows:
<seg type="sentence" ana="SVO">
<seg type="lex" ana="#NP1">John</seg>
<seg type="lex" ana="#VVI">loves</seg>
<seg type="lex" ana="#NP1">Nancy</seg>
</seg>
This encoding implies the existence elsewhere in the document of elements with identifiers SVO, NP1, and VV1 where the significance of these particular codes is explained. Note the use of the <seg> element to mark particular components of the analysis, distinguished by the type attribute.The corresp (corresponding) attribute provides a simple way of representing some form of correspondence between two elements in a text. For example, in a multilingual text, it may be used to link translation equivalents, as in the following example
<seg xml:lang="fr" xml:id="FR1"
corresp="#EN1">Jean
aime Nancy</seg>
<seg xml:lang="en" xml:id="EN1"
corresp="#FR1">John loves
Nancy</seg>
The same mechanism may be used for a variety of purposes. In the following example, it has been used to represent the correspondences between the show and ‘Shirley’, and between ‘NBC’ and ‘the network’:
<p>
<title xml:id="shirley">Shirley</title>, which
made its Friday night debut only a month ago, was not listed on <name xml:id="nbc">NBC</name>'s new schedule, although <seg xml:id="network" corresp="#nbc">the network</seg>
says <seg xml:id="show" corresp="#shirley">the show</seg> still is being
considered.
</p>
The next and prev attributes provide a simple way of linking together the components of a discontinuous element, as in the following example:
<q xml:id="Q1a" next="#Q1b">Who-e debel you?</q> —
he at last said — <q xml:id="Q1b" prev="#Q1a">you no speak-e, damme, I kill-e.</q> And so
saying, the lighted tomahawk began flourishing about me in the dark.
3.7.4. <ab> and <seg> as basic block and inline elements
The <seg> has been part of TEI from the very beginning. It is a purely formal inline element that operates at the level of words and phrases and below <block> elements, such as paragraphs. You could say that other inline elements, such as <hi>, <w>, <c>, <foreign>, <name>, etc. are merely syntactic sugar for <seg> elements with appropriate type attributes such as <seg type="foreign">. The rules for its use are relatively straightforward. You may use it for any segmentation at the word or phrase level for which no explicit element exists. You should not use it where there is an appropriate element. <seg type="hi"> is valid but silly.
The <ab> element was not part of the original element set, but was added in 1997. It is defined as an anonymous block that ‘contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3 Blocks, Segments, and Anchors]’. Thus <ab> is at one level opposed to seg (block vs. inline) and on another level to p (like <p> but without its ‘semantic baggage’).
By the time <ab> was introduced encoders had been happily using <p> not just for paragraphs but for any ‘chunk of prose’, as one TEI veteran has put it. In practice TEI <p> may not have been as different from HTML <p> as it should have been. A lot of stuff inside <p> has none of the semantic baggage associated with paragraphs.
That said, a recent survey (October 2015) produced a variety of use cases that may help encoders decide whether <ab> or <p> is more appropriate for a given ‘chunk of prose’. The<ab> element has been used for:
- The canonical verses of the Bible, first produced in the Stephanus edition of 1571
- Greek inscriptions created in a world that had not yet invented paragraphs
- Hieroglyphic texts, which have no semantic sense of a paragraph
- Texts where the divisions into chunks are conventional (and differ between witnesses), and have been provided by medieval scribes
- notebooks written by a contemporary artist, containing a lot of fragmentary and unstructured notes expressing thoughts and ideas (text and graphics) which are often just single words, unfinished sentences or sketches, and unrelated to previous or following entries.
- rubrics or interspersed commentary in liturgical texts
- The question and answer structure of catechisms as well as the alternating structures common in 17th century polemtical literature
- table-like content that cannot be wrangled into a row/column structure and where <ab type="tabular" xml:space="preserve"> is the best you can do
- machine-based encoding of PDF or OCR files
Finally, <p> has been a useful element for identifying prose in dramatic dialogue, whether or not it is conducted in paragraphs, which it usually is not. Whether a speech in a play is in prose or verse is not always to tell. When Gertrude says ‘The lady does protest too much methinks’ her words happen to scan but are surrounded by prose.If you want avoid jumping off the fence you could use <ab>. The list could go on and certainly demonstrates that a lot of prose does not come in paragraphs with semantic baggage. The "Best Practices for TEI in Libraries" offers a somewhat off-beat use of <ab> as an answer to the question how to encode asterisks or similar horizontally oriented symbols that mark some degree of separation between the stuff below and above. They recommend <ab type="typography"> * * * </ab> instead of <milestone type="separator" unit="undetermined" rend="stars"/> on the grounds that for many users this direct representation of asterisks will be more intuitive than representing them as attribute values.
3.8. Editorial Interventions
The process of encoding an electronic text has much in common with the process of editing a manuscript or other text for printed publication. In either case a conscientious editor may wish to record both the original state of the source and any editorial correction or other change made in it. The elements discussed in this and the next section provide some facilities for meeting these needs.
3.8.1. Correction and Normalization
The following elements may be used to mark correction, that is editorial changes introduced where the editor believes the original to be erroneous:
- corr (correction) contains the correct form of a passage apparently erroneous in the copy text.
- sic (Latin for thus or so ) contains text reproduced although apparently incorrect or inaccurate.
The following elements may be used to mark normalization, that is editorial changes introduced for the sake of consistency or modernization of a text:
- orig (original form) contains a reading which is marked as following the original, rather than being normalized or corrected.
- reg (regularization) contains a reading which has been regularized or normalized in some sense.
As an example, consider this extract from the quarto printing of Shakespeare's Henry V.
... for his nose was as sharp as a pen and a table of green feelds
A modern editor might wish to make a number of interventions here, specifically to modernize (or normalise) the Elizabethan spellings of a' and feelds for he and fields respectively. He or she might also want to emend table to babbl'd, following an editorial tradition that goes back to the 18th century Shakespearian scholar Lewis Theobald. The following encoding would then be appropriate:
... for his nose was as sharp as
a pen and <reg>he</reg>
<corr resp="#Theobald">babbl'd</corr> of green
<reg>fields</reg>
A more conservative or source-oriented editor, however, might want to retain the original, but at the same time signal that some of the readings it contains are in some sense anomalous:
... for his nose was as sharp as a pen and
<orig>a</orig>
<sic>table</sic> of green
<orig>feelds</orig>
Finally, a modern digital editor may decide to combine both possibilities in a single composite text, using the <choice> element.
- choice groups a number of alternative encodings for the same point in a text.
... for his nose was as sharp as a pen and
<choice>
<orig>a</orig>
<reg>he</reg>
</choice>
<choice>
<corr resp="#Theobald">babbl'd</corr>
<sic>table</sic>
</choice> of green
<choice>
<orig>feelds</orig>
<reg>fields</reg>
</choice>
3.8.2. Omissions, Deletions, and Additions
In addition to correcting or normalizing words and phrases, editors and transcribers may also supply missing material, omit material, or transcribe material deleted or crossed out in the source. In addition, some material may be particularly hard to transcribe because it is hard to make out on the page. The following elements may be used to record such phenomena:
- add (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector.
- gap indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible.
- del (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector.
- unclear contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source.
These elements may be used to record changes made by an editor, by the transcriber, or (in manuscript material) by the author or scribe. For example, if the source for an electronic text read ‘The following elements are provided for for simple editorial interventions.’ then it might be felt desirable to correct the obvious error, but at the same time to record the deletion of the superfluous second for, thus:
The following elements are provided for <del resp="#LB">for</del> simple editorial interventions.
The attribute value #LB on the resp attribute is used to point to a fuller definition (typically in a <respStmt> element) for the agency responsible for correcting the duplication of for.If the source read ‘The following elements provided for simple editorial interventions.’ (i.e. if the verb had been inadvertently dropped) then the corrected text might read:
The following elements <add resp="#LB">are</add> provided for simple editorial interventions.
These elements are also used to record authorial changes in manuscripts. A manuscript in which the author has first written ‘How it galls me, what a galling shadow’, then crossed out the word galls and inserted dogs might be encoded thus:
How it <del hand="#DHL" type="overstrike">galls</del>
<add hand="#DHL" place="supralinear">dogs</add> me, what a galling shadow
Again, the code #DHL points to another location where more information about the hand concerned is to be found2.Similarly, the <unclear> and <gap> elements may be used together to indicate the omission of illegible material; the following example also shows the use of <add> for a conjectural emendation:
One hundred
& twenty good regulars joined to me <unclear>
<gap reason="indecipherable"/>
</unclear>
& instantly, would aid me signally <add hand="#ed">in?</add> an enterprise against
Wilmington.
The <del> element marks material which has been transcribed as part of the electronic text despite being marked as deleted, while <gap> marks the location of material which is omitted from the electronic text, whether it is legible or not. A language corpus, for example, might omit long quotations in foreign languages:
<p> ... An example of a list appearing in a fief
ledger of <name type="place">Koldinghus</name>
<date>1611/12</date> is given below. It shows cash income from a sale of
honey.</p>
<gap>
<desc>quotation from ledger (in Danish)</desc>
</gap>
<p>A description of the
overall structure of the account is once again ... </p>
Other corpora (particular those constructed before the widespread use of scanners) systematically omit figures and mathematics:
<p>At the bottom of your screen below the mode line is the <term>minibuffer</term>. This is
the area where Emacs echoes the commands you enter and where you specify filenames for Emacs
to find, values for search and replace, and so on. <gap reason="graphic">
<desc>diagram of
Emacs screen</desc>
</gap>
</p>
3.8.3. Abbreviations and their Expansion
Like names, dates, and numbers, abbreviations may be transcribed as they stand or expanded; they may be left unmarked, or encoded using the following elements:
- abbr (abbreviation) contains an abbreviation of any sort.
- expan (expansion) contains the expansion of an abbreviation.
The <abbr> element is useful as a means of distinguishing semi-lexical items such as acronyms or jargon:
We can sum up the above
discussion as follows: the identity of a <abbr>CC</abbr> is defined by that calibration of
values which motivates the elements of its <abbr>GSP</abbr>;
Every manufacturer of <abbr>3GL</abbr> or
<abbr>4GL</abbr> languages is currently nailing on <abbr>OOP</abbr> extensions
The type attribute may be used to distinguish types of abbreviation by their function.
The <expan> element is used to mark an expansion supplied by an encoder. This element is particularly useful in the transcription of manuscript materials. For example, the character p with a bar through its descender as a conventional representation for the word per is commonly encountered in Medieval European manuscripts. An encoder may choose to expand this as follows:
<expan>per</expan>
To record both an abbreviation and its expansion, the <choice> element mentioned above may be used to group the abbreviated form with its proposed expansion:
<choice>
<abbr>wt</abbr>
<expan>with</expan>
</choice>
For a fuller discussion of abbreviations and the intricacies of representing them consult the section on Abbreviations and Expansion in the Guidelines.3.9. Names, Dates, and Numbers
The TEI scheme defines elements for a large number of ‘data-like’ features which may appear almost anywhere within almost any kind of text. These features may be of particular interest in a range of disciplines; they all relate to objects external to the text itself, such as the names of persons and places, numbers and dates. They also pose particular problems for many natural language processing (NLP) applications because of the variety of ways in which they may be presented within a text. The elements described here, by making such features explicit, reduce the complexity of processing texts containing them.
3.9.1. Names and Referring Strings
A referring string is a phrase which refers to some person, place, object, etc. Two elements are provided to mark such strings:
- rs (referencing string) contains a general purpose name or referring string.
- name (name, proper noun) contains a proper noun or noun phrase.
The type attribute is used to distinguish amongst (for example) names of persons, places and organizations, where this is possible:
<q>My dear <rs type="person">Mr. Bennet</rs>, </q>
said his lady to him one day,
<q>have you heard that <rs type="place">Netherfield Park</rs>
is let at last?</q>
It being one of the principles of the <rs type="organization">Circumlocution Office</rs> never, on any account whatsoever, to give a
straightforward answer, <rs type="person">Mr Barnacle</rs> said,
<q>Possibly.</q>
As the following example shows, the <rs> element may be used for any reference to a person, place, etc, not necessarily one in the form of a proper noun or noun phrase.
<q>My dear <rs type="person">Mr. Bennet</rs>,</q>
said <rs type="person">his lady</rs> to him one day...
The <name> element by contrast is provided for the special case of referencing strings which consist only of proper nouns; it may be used synonymously with the <rs> element, or nested within it if a referring string contains a mixture of common and proper nouns.
Simply tagging something as a name is rarely enough to enable automatic processing of personal names into the canonical forms usually required for reference purposes. The name as it appears in the text may be inconsistently spelled, partial, or vague. Moreover, name prefixes such as van or de la, may or may not be included as part of the reference form of a name, depending on the language and country of origin of the bearer.
The key attribute provides an alternative normalized identifier for the object being named, like a database record key. It may thus be useful as a means of gathering together all references to the same individual or location scattered throughout a document:
<q>My dear <rs type="person" key="BENM1">Mr.
Bennet</rs>, </q> said <rs type="person" key="BENM2">his lady</rs> to him one day,
<q>have
you heard that <rs type="place" key="NETP1">Netherfield Park</rs> is let at
last?</q>
This use should be distinguished from the case of the <reg> (regularization) element, which provides a means of marking the standard form of a referencing string as demonstrated below:
<name type="person" key="WADLM1">
<choice>
<sic>Walter de la Mare</sic>
<reg>de la Mare, Walter</reg>
</choice>
</name> was
born at <name key="Ch1" type="place">Charlton</name>, in <name key="KT1" type="county">Kent</name>, in 1873.
3.9.2. Dates and Times
Tags for the more detailed encoding of times and dates include the following:
These elements have a number of attributes which can be used to provide normalised versions of their values.
- att.datable provides attributes for normalization of elements that contain dates, times, or datable events.
calendar indicates the system or calendar to which the date represented by the content of this element belongs. period supplies a pointer to some location defining a named period of time within which the datable item is understood to have occurred. when [att.datable.w3c] supplies the value of the date or time in a standard form, e.g. yyyy-mm-dd.
<date when="1980-02-21">21
Feb 1980</date>
<date when="1990">1990</date>
<date when="1990-09">September 1990</date>
<date when="--09">September</date>
<date when="2001-09-11T12:48:00">Sept 11th, 12 minutes before 9
am</date>
Note in the last example the use of a normalized representation for the date string which includes a time: this example could thus equally well be tagged using the <time> element.Given on the <date when="1977-06-12">Twelfth
Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the
Republic the Two Hundredth and first and of the University the Eighty-Sixth.</date>
<l>specially when it's nine below zero</l>
<l>and <time when="15:00:00">three o'clock in the afternoon</time>
</l>
3.9.3. Numbers
Numbers can be written with either letters or digits (twenty-one, xxi, and 21) and their presentation is language-dependent (e.g. English 5th becomes Greek 5.; English 123,456.78 equals French 123.456,78). In natural-language processing or machine-translation applications, it is often helpful to distinguish them from other, more ‘lexical’ parts of the text. In other applications, the ability to record a number's value in standard notation is important. The <num> element provides this possibility:
- num (number) contains a number, written in any form.
For example:
<num value="33">xxxiii</num>
<num type="cardinal" value="21">twenty-one</num>
<num type="percentage" value="10">ten percent</num>
<num type="percentage" value="10">10%</num>
<num type="ordinal" value="5">5th</num>
3.10. Lists
The element <list> is used to mark any kind of list. A list is a sequence of text items, which may be numbered, bulleted, or arranged as a glossary list. Each item may be preceded by an item label (in a glossary list, this label is the term being defined):
- list contains any sequence of items organized as a list.
- item contains one component of a list.
- label contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.
Individual list items are tagged with <item>. The first <item> may optionally be preceded by a <head>, which gives a heading for the list. The numbering of a list may be omitted, indicated using the n attribute on each item, or (rarely) tagged as content using the <label> element. The following are all thus equivalent:
<list>
<head>A short list</head>
<item>First item in list.</item>
<item>Second item in list.</item>
<item>Third item in list.</item>
</list>
<list>
<head>A short list</head>
<item n="1">First item in list.</item>
<item n="2">Second item in list.</item>
<item n="3">Third item in list.</item>
</list>
<list>
<head>A short list</head>
<label>1</label>
<item>First item in list.</item>
<label>2</label>
<item>Second item in list.</item>
<label>3</label>
<item>Third item in list.</item>
</list>
The styles should not be mixed in the same list.A simple two-column table may be treated as a glossary list, tagged
<list type="gloss">. Here, each item comprises a term and a gloss, marked with <label> and <item> respectively. These correspond to the elements <term> and <gloss>, which can occur anywhere in prose text. <list type="gloss">
<head>Vocabulary</head>
<label xml:lang="enm">nu</label>
<item>now</item>
<label xml:lang="enm">lhude</label>
<item>loudly</item>
<label xml:lang="enm">bloweth</label>
<item>blooms</item>
<label xml:lang="enm">med</label>
<item>meadow</item>
<label xml:lang="enm">wude</label>
<item>wood</item>
<label xml:lang="enm">awe</label>
<item>ewe</item>
<label xml:lang="enm">lhouth</label>
<item>lows</item>
<label xml:lang="enm">sterteth</label>
<item>bounds, frisks</item>
<label xml:lang="enm">verteth</label>
<item xml:lang="la">pedit</item>
<label xml:lang="enm">murie</label>
<item>merrily</item>
<label xml:lang="enm">swik</label>
<item>cease</item>
<label xml:lang="enm">naver</label>
<item>never</item>
</list>
Where the internal structure of a list item is more complex, it may be preferable to regard the list as a table, for which special-purpose tagging is defined below (3.12. Tables).
Lists of whatever kind can, of course, nest within list items to any depth required. Here, for example, a glossary list contains two items, each of which is itself a simple list:
<list type="gloss">
<label>EVIL</label>
<item>
<list type="simple">
<item>I am cast upon a horrible desolate island, void of all hope of recovery.</item>
<item>I am singled out and separated as it were from all the world to be miserable.</item>
<item>I am divided from mankind — a solitaire; one banished from human society.</item>
</list>
</item>
<label>GOOD</label>
<item>
<list type="simple">
<item>But I am alive; and not drowned, as all my ship's company were.</item>
<item>But I am singled out, too, from all the ship's crew, to be spared from
death...</item>
<item>But I am not starved, and perishing on a barren place, affording no
sustenances....</item>
</list>
</item>
</list>
A list need not necessarily be displayed in list format. For example,
<p>On those remote pages it is written that animals
are divided into <list rendition="run-on">
<item n="a">those that belong to the Emperor,</item>
<item n="b"> embalmed ones, </item>
<item n="c"> those that are trained, </item>
<item n="d"> suckling pigs, </item>
<item n="e"> mermaids, </item>
<item n="f"> fabulous ones, </item>
<item n="g"> stray dogs, </item>
<item n="h"> those that are included in this classification, </item>
<item n="i"> those that tremble as if they were mad, </item>
<item n="j"> innumerable ones, </item>
<item n="k"> those drawn with a very fine camel's-hair brush, </item>
<item n="l"> others, </item>
<item n="m"> those that have just broken a flower vase, </item>
<item n="n"> those that resemble flies from a distance.</item>
</list>
</p>
Lists of bibliographic items should be tagged using the <listBibl> element, described in the next section.
3.11. Bibliographic Citations
It is often useful to distinguish bibliographic citations where they occur within texts being transcribed for research, if only so that they will be properly formatted when the text is printed out. The element <bibl> is provided for this purpose. Where the components of a bibliographic reference are to be distinguished, the following elements may be used as appropriate. It is generally useful to mark at least those parts (such as the titles of articles, books, and journals) which will need special formatting. The other elements are provided for cases where particular interest attaches to such details.
- bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
- author in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority.
- biblScope (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work.
- date contains a date in any format.
- editor contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc.
- publisher provides the name of the organization responsible for the publication or distribution of a bibliographic item.
- pubPlace (publication place) contains the name of the place where a bibliographic item was published.
- title contains a title for any kind of work.
For example, the following editorial note might be transcribed as shown: He was a member of Parliament for Warwickshire in 1445, and died March 14, 1470 (according to Kittredge, Harvard Studies 5. 88ff).
He was a member of Parliament for Warwickshire
in 1445, and died March 14, 1470 (according to <bibl>
<author>Kittredge</author>,
<title>Harvard Studies</title> 5. 88ff
</bibl>).
For lists of bibliographic citations, the <listBibl> element should be used; it may contain a series of <bibl> elements.
3.12. Tables
Tables represent a challenge for any text processing system, but simple tables, at least, appear in so many texts that even in the simplified TEI tag set presented here, markup for tables is necessary. The following elements are provided for this purpose:
- table contains text displayed in tabular form, in rows and columns.
- row contains one row of a table.
- cell contains one cell of a table.
For example, Defoe uses mortality tables like the following in the Journal of the Plague Year to show the rise and ebb of the epidemic:
<p>It was indeed coming on amain, for the burials
that same week were in the next adjoining parishes thus:— <table rows="5" cols="4">
<row role="data">
<cell role="label">St. Leonard's, Shoreditch</cell>
<cell>64</cell>
<cell>84</cell>
<cell>119</cell>
</row>
<row role="data">
<cell role="label">St. Botolph's, Bishopsgate</cell>
<cell>65</cell>
<cell>105</cell>
<cell>116</cell>
</row>
<row role="data">
<cell role="label">St. Giles's, Cripplegate</cell>
<cell>213</cell>
<cell>421</cell>
<cell>554</cell>
</row>
</table>
</p>
<p>This shutting up of houses was at first counted a very cruel and unchristian
method, and the poor people so confined made bitter lamentations. ... </p>
3.13. Figures and Graphics
Not all the components of a document are necessarily textual. The most straightforward text will often contain diagrams or illustrations, to say nothing of documents in which image and text are inextricably intertwined, or electronic resources in which the two are complementary.
The encoder may simply record the presence of a graphic within the text, possibly with a brief description of its content, and may also provide a link to a digitized version of the graphic, using the following elements:
- graphic indicates the location of an inline graphic, illustration, or figure.
- figure groups elements representing or containing graphic information such as an illustration, formula, or figure.
- figDesc (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it.
Any textual information accompanying the graphic, such as a heading and/or caption, may be included within the <figure> element itself, in a <head> and one or more <p> elements, as also may any text appearing within the graphic itself. It is strongly recommended that a prose description of the image be supplied, as the content of a <figDesc> element, for the use of applications which are not able to render the graphic, and to render the document accessible to vision-impaired readers. (Such text is not normally considered part of the document proper.)
The simplest use for these elements is to mark the position of a graphic and provide a link to it, as in this example;
<pb n="412"/>
<figure>
<graphic url="p412fig.png"/>
</figure>
<pb n="413"/>
This indicates that the graphic contained by the file p412fig.png appears between pages 412 and 413.The <graphic> element can appear anywhere that textual content is permitted, within but not between paragraphs or headings. In the following example, the encoder has decided to treat a specific printer's ornament as a heading:
<head>
<graphic url="http://www.iath.virginia.edu/gants/Ornaments/Heads/hp-ral02.gif"/>
</head>
More usually, a graphic will have at the least an identifying title, which may be encoded using the <head> element, or a number of figures may be grouped together in a particular structure. It is also often convenient to include a brief description of the image. The <figure> element provides a means of wrapping one or more such elements together as a kind of graphic ‘block’:
<figure>
<graphic url="fessipic.png"/>
<head>Mr Fezziwig's Ball</head>
<figDesc>A Cruikshank
engraving showing Mr Fezziwig leading a group of revellers.</figDesc>
</figure>
These cases should be carefully distinguished from the case where an encoded text is complemented by a collection of digital images, maintained as a distinct resource. The facs attribute may be used to associate any element in an encoded text with a digital facsimile of it. In the simple case where only page images are available, the facs attribute on the <pb/> element may be used to associate each image with an appropriate point in the text:
<text>
<pb facs="page1.png" n="1"/>
<!-- text contained on page 1 is encoded here -->
<pb facs="page2.png" n="2"/>
<!-- text contained on page 2 is encoded here -->
</text>
This method is only appropriate in the simple case where each digital image file page1.png etc. corresponds with a single transcribed and encoded page. If more detailed alignment of image and transcription is required, for example because the image files actually represent double page spreads, more sophisticated mechanisms are provided in the full TEI Guidelines.3.14. Analysis
3.14.1. Orthographic Sentences
Interpretation typically ranges across the whole of a text, with no particular respect to other structural units. A useful preliminary to intensive interpretation is therefore to segment the text into discrete and identifiable units, each of which can then bear a label for use as a sort of ‘canonical reference’. To facilitate such uses, these units may not cross each other, nor nest within each other. They may conveniently be represented using the following element:
- s (s-unit) contains a sentence-like division of a text.
As the name suggests, the <s> element is most commonly used (in linguistic applications at least) for marking orthographic sentences, that is, units defined by orthographic features such as punctuation. For example, the passage from Jane Eyre discussed earlier might be divided into s-units as follows:
<pb n="474"/>
<div type="chapter" n="38">
<p>
<s n="001">Reader, I married him.</s>
<s n="002">A quiet wedding we had:</s>
<s n="003">he
and I, the parson and clerk, were alone present.</s>
<s n="004">When we got back from
church, I went into the kitchen of the manor-house, where Mary was cooking the dinner, and
John cleaning the knives, and I said —</s>
</p>
<p>
<q>
<s n="005">Mary, I have been married to Mr Rochester this morning.</s>
</q> ... </p>
</div>
Note that <s> elements cannot nest: the beginning of one <s> element implies that the previous one has finished. When s-units are tagged as shown above, it is advisable to tag the entire text end-to-end, so that every word in the text being analysed will be contained by exactly one <s> element, whose identifier can then be used to specify a unique reference for it. If the identifiers used are unique within the document, then the xml:id attribute might be used in preference to the n attribute used in the above example.3.14.2. Words and punctuation
Tokenization, that is, the identification of lexical or non-lexical tokens within a text, is a very common requirement for all kinds of textual analysis, and not an entirely trivial one. The decision as to whether, for example, ‘can't’ in English or ‘du’ in French should be treated as one word or two is not simple. Consequently it is often useful to make explicit the preferred tokenization in a marked up text. The following elements are available for this purpose:
- w (word) represents a grammatical (not necessarily orthographic) word.
- pc (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark.
For example, the output from a part of speech tagger might be recorded in TEI Lite as follows:
<s n="1">
<w ana="#NP0">Marley</w>
<w ana="#VBD">was</w>
<w ana="#AJ0">dead</w>
<pc>:</pc>
<w ana="#TO0">to</w>
<w ana="#VBB">begin</w>
<w ana="#PRP">with</w>
<pc>. </pc>
</s>
In this example, each word has been decorated with an automatically generated part of speech code, using the ana attribute discussed in section 3.7.3. Special kinds of Linking above. The <w> also provides for each word to be associated with a root form or lemma, either explicitly using the lemma attribute, or by reference, using the lemmaRef attribute, as in this example:
...<w ana="#VBD" lemma="be"
lemmaRef="http://www.myLexicon.com/be">was</w> ...
3.14.3. General-Purpose Interpretation Elements
The <w> element is a specialisation of the <seg> element which has already been introduced for use in identifying otherwise unmarked targets of cross references and hypertext links (see section 3.7. Cross References and Links); it identifies some phrase-level portion of text to which the encoder may assign a user-specified type, as well as a unique identifier; it may thus be used to tag textual features for which there is no other provision in the published TEI Guidelines.
For example, the Guidelines provide no ‘apostrophe’ element to mark parts of a literary text in which the narrator addresses the reader (or hearer) directly. One approach might be to regard these as instances of the <q> element, distinguished from others by an appropriate value for the who attribute. A possibly simpler, and certainly more general, solution would however be to use the <seg> element as follows:
<div type="chapter" n="38">
<p>
<seg type="apostrophe">Reader, I married him.</seg> A quiet wedding we had: ...</p>
</div>
The type attribute on the <seg> element can take any value, and so can be used to record phrase-level phenomena of any kind; it is good practice to record the values used and their significance in the header.3.15.
A composite text also has an optional front and back. In between occur one or more groups of texts, each with its own optional front and back matter. A composite text will thus be encoded using an overall structure like this:
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<!--[ header information for the composite ]-->
</teiHeader>
<text>
<front>
<!--[ front matter for the composite ]-->
</front>
<group>
<text>
<front>
<!--[ front matter of first text ]-->
</front>
<body>
<!--[ body of first text ]-->
</body>
<back>
<!--[ back matter of first text ]-->
</back>
</text>
<text>
<front>
<!--[ front matter of second text]-->
</front>
<body>
<!--[ body of second text ]-->
</body>
<back>
<!--[ back matter of second text ]-->
</back>
</text>
<!--[ more texts or groups of texts here ]-->
</group>
<back>
<!--[ back matter for the composite ]-->
</back>
</text>
</TEI>
It is also possible to define a composite of complete TEI texts, each with its own header. Such a collection is known as a TEI corpus, and must itself have a header:
<teiCorpus xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<!--[header information for the corpus]-->
</teiHeader>
<TEI>
<teiHeader>
<!--[header information for first text]-->
</teiHeader>
<text>
<!--[first text in corpus]-->
</text>
</TEI>
<TEI>
<teiHeader>
<!--[header information for second text]-->
</teiHeader>
<text>
<!--[second text in corpus]-->
</text>
</TEI>
</teiCorpus>
It is also possible to create a composite of corpora -- that is, one <teiCorpus> element may contain many nested <teiCorpus> elements rather than many nested <TEI> elements, to any depth considered necessary.3.16. Front and Back Matter
3.16.1. Front Matter
For many purposes, particularly in older texts, the preliminary material such as title pages, prefatory epistles, etc., may provide very useful additional linguistic or social information. P5 provides a set of recommendations for distinguishing the textual elements most commonly encountered in front matter, which are summarized here.
3.16.1.1. Title Page
The start of a title page should be marked with the element <titlePage>. All text contained on the page should be transcribed and tagged with the appropriate element from the following list:
- titlePage (title page) contains the title page of a text, appearing within the front or back matter.
- docTitle (document title) contains the title of a document, including all its constituents, as given on a title page.
- titlePart contains a subsection or division of the title of a work, as indicated on a title page.
- byline contains the primary statement of responsibility given for a work on its title page or at the head or end of the work.
- docAuthor (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline).
- docDate (document date) contains the date of a document, as given on a title page or in a dateline.
- docEdition (document edition) contains an edition statement as presented on a title page of a document.
- docImprint (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page.
- epigraph contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page.
Typeface distinctions should be marked with the rendition attribute when necessary, as described above. Very detailed description of the letter spacing and sizing used in ornamental titles is not as yet provided for by the Guidelines. Changes of language should be marked by appropriate use of the xml:lang attribute or the <foreign> element, as necessary. Names of people, places, or organizations, may be tagged using the <name> element wherever they appear if no other more specific element is available.
Two example title pages follow:
<titlePage rendition="Roman">
<docTitle>
<titlePart type="main"> PARADISE REGAIN'D. A POEM In IV <hi>BOOKS</hi>. </titlePart>
<titlePart> To which is added <title>SAMSON AGONISTES</title>. </titlePart>
</docTitle>
<byline>The Author <docAuthor>JOHN MILTON</docAuthor>
</byline>
<docImprint>
<name>LONDON</name>, Printed by <name>J.M.</name> for <name>John Starkey</name>
at the <name>Mitre</name> in <name>Fleetstreet</name>, near
<name>Temple-Bar.</name>
</docImprint>
<docDate>MDCLXXI</docDate>
</titlePage>
<titlePage>
<docTitle>
<titlePart type="main"> Lives of the Queens of England, from the Norman
Conquest;</titlePart>
<titlePart type="sub">with anecdotes of their courts. </titlePart>
</docTitle>
<titlePart>Now first published from Official Records and other authentic documents private
as well as public.</titlePart>
<docEdition>New edition, with corrections and additions</docEdition>
<byline>By <docAuthor>Agnes Strickland</docAuthor>
</byline>
<epigraph>
<q>The treasures of antiquity laid up in old historic rolls, I opened.</q>
<bibl>BEAUMONT</bibl>
</epigraph>
<docImprint>Philadelphia: Blanchard and Lea</docImprint>
<docDate>1860.</docDate>
</titlePage>
As elsewhere, the ref attribute may be used to link a name with a canonical definition of the entity being named. For example:
<byline>By <docAuthor>
<name ref="http://en.wikipedia.org/wiki/Agnes_Strickland">Agnes
Strickland</name>
</docAuthor>
</byline>
3.16.1.2. Prefatory Matter
Major blocks of text within the front matter should be marked using <div> elements; the following suggested values for the type attribute may be used to distinguish various common types of prefatory matter:
- preface
- A foreword or preface addressed to the reader in which the author or publisher explains the content, purpose, or origin of the text
- dedication
- A formal offering or dedication of a text to one or more persons or institutions by the author.
- abstract
- A summary of the content of a text as continuous prose
- ack
- A formal declaration of acknowledgment by the author in which persons and institutions are thanked for their part in the creation of a text
- contents
- A table of contents, specifying the structure of a work and listing its constituents. The <list> element should be used to mark its structure.
- frontispiece
- A pictorial frontispiece, possibly including some text.
Where other kinds of prefatory matter are encountered, the encoder is at liberty to invent other values for the type attribute.
Like any text division, those in front matter may contain low level structural or non-structural elements as described elsewhere. They will generally begin with a heading or title of some kind which should be tagged using the <head> element. Epistles will contain the following additional elements:
- salute (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc.
- signed (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text.
- byline contains the primary statement of responsibility given for a work on its title page or at the head or end of the work.
- dateline contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer.
- argument contains a formal list or prose description of the topics addressed by a subdivision of a text.
- cit (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example.
- imprimatur contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso.
- opener groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter.
- closer groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter.
Epistles which appear elsewhere in a text will, of course, contain these same elements.
As an example, the dedication at the start of Milton's Comus should be marked up as follows:
<div type="dedication">
<head>To the Right Honourable <name>JOHN Lord Viscount BRACLY</name>, Son and Heir apparent
to the Earl of Bridgewater, &c.</head>
<salute>MY LORD,</salute>
<p>THis <hi>Poem</hi>, which receiv'd its first occasion of Birth from your Self, and
others of your Noble Family .... and as in this representation your attendant
<name>Thyrsis</name>, so now in all reall expression</p>
<closer>
<salute>Your faithfull, and most humble servant</salute>
<signed>
<name>H. LAWES.</name>
</signed>
</closer>
</div>
3.16.2. Back Matter
3.16.2.1. Structural Divisions of Back Matter
Because of variations in publishing practice, back matter can contain virtually any of the elements listed above for front matter, and the same elements should be used where this is so. Additionally, back matter may contain the following types of matter within the <back> element. Like the structural divisions of the body, these should be marked as <div> elements, and distinguished by the following suggested values of the type attribute:
- appendix
- An ancillary self-contained section of a work, often providing additional but in some sense extra-canonical text.
- glossary
- A list of terms associated with definition texts (‘glosses’): this should be encoded as a <<list type="gloss">> element
- notes
- A section in which textual or other kinds of notes are gathered together.
- bibliogr
- A list of bibliographic citations: this should be encoded as a <listBibl>
- index
- Any form of pre-existing index to the work (An index may also be generated for a document by using the <index> element described above).
- colophon
- A statement appearing at the end of a book describing the conditions of its physical production.
3.17. The Electronic Title Page
Every TEI text has a header which provides information analogous to that provided by the title page of printed text. The header is introduced by the element <teiHeader> and has four major parts:
- fileDesc (file description) contains a full bibliographic description of an electronic file.
- encodingDesc (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived.
- profileDesc (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting.
- revisionDesc (revision description) summarizes the revision history for a file.
A corpus or collection of texts with many shared characteristics may have one header for the corpus and individual headers for each component of the corpus. In this case the type attribute indicates the type of header. <teiHeader type="corpus"> introduces the header for corpus-level information.
Some of the header elements contain running prose which consists of one or more <p>s. Others are grouped:
- Elements whose names end in Stmt (for statement) usually enclose a group of elements recording some structured information.
- Elements whose names end in Decl (for declaration) enclose information about specific encoding practices.
- Elements whose names end in Desc (for description) contain a prose description.
3.17.1. The File Description
The <fileDesc> element is mandatory. It contains a full bibliographic description of the file with the following elements:
- titleStmt (title statement) groups information about the title of a work and those responsible for its content.
- editionStmt (edition statement) groups information relating to one edition of a text.
- extent describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units.
- publicationStmt (publication statement) groups information concerning the publication or distribution of an electronic or other text.
- seriesStmt (series statement) groups information about the series, if any, to which a publication belongs.
- notesStmt (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description.
- sourceDesc (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence.
A minimal header has the following structure:
<teiHeader>
<fileDesc>
<titleStmt>
<!-- bibliographic description of the digital resource -->
</titleStmt>
<publicationStmt>
<!-- information about how the resource is distributed -->
</publicationStmt>
<sourceDesc>
<!-- information about the sources from which the digital resource is derived -->
</sourceDesc>
</fileDesc>
</teiHeader>
3.17.1.1. The Title Statement
The following elements can be used in the <titleStmt>:
- title contains a title for any kind of work.
- author in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority.
- sponsor specifies the name of a sponsoring organization or institution.
- funder (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text.
- principal (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text.
- respStmt (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work.
The title of a digital resource derived from a non-digital one will obviously be similar. However, it is important to distinguish the title of the computer file from that of the source text, for example:
[title of source]: a machine readable transcription [title of source]: electronic edition A machine readable version of: [title of source]The <respStmt> element contains the following subcomponents:
- resp (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work.
- name (name, proper noun) contains a proper noun or noun phrase.
<titleStmt>
<title>Two stories by Edgar Allen Poe: a machine readable transcription</title>
<author>Poe, Edgar Allen (1809-1849)</author>
<respStmt>
<resp>compiled by</resp>
<name>James D. Benson</name>
</respStmt>
</titleStmt>
3.17.1.2. The Edition Statement
The <editionStmt> groups information relating to one edition of the digital resource (where edition is used as elsewhere in bibliography), and may include the following elements:
- edition describes the particularities of one edition of a text.
- respStmt (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work.
Example:
<editionStmt>
<edition n="U2">Third
draft, substantially revised <date>1987</date>
</edition>
</editionStmt>
Determining exactly what constitutes a new edition of an electronic text is left to the encoder.
3.17.1.3. The Extent Statement
The <extent> statement describes the approximate size of the digital resource.
Example:
<extent>4532
bytes</extent>
3.17.1.4. The Publication Statement
The <publicationStmt> is mandatory. It may contain a simple prose description or groups of the elements described below:
- publisher provides the name of the organization responsible for the publication or distribution of a bibliographic item.
- distributor supplies the name of a person or other agency responsible for the distribution of a text.
- authority (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor.
At least one of these three elements must be present, unless the entire publication statement is in prose. The following elements may occur within them:
- pubPlace (publication place) contains the name of the place where a bibliographic item was published.
- address contains a postal address, for example of a publisher, an organization, or an individual.
- idno (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way.
- availability supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc.
- licence contains information about a licence or other legal agreement applicable to the text.
- date contains a date in any format.
Example:
<publicationStmt>
<publisher>University of Victoria Humanities Computing and Media Centre</publisher>
<pubPlace>Victoria, BC</pubPlace>
<date>2011</date>
<availability status="restricted">
<licence target="http://creativecommons.org/licenses/by-sa/3.0/"> Distributed under a
Creative Commons Attribution-ShareAlike 3.0 Unported License </licence>
</availability>
</publicationStmt>
3.17.1.5. Series and Notes Statements
The <seriesStmt> element groups information about the series, if any, to which a publication belongs. It may contain <title>, <idno>, or <respStmt> elements.
The <notesStmt>, if used, contains one or more <note> elements which contain a note or annotation. Some information found in the notes area in conventional bibliography has been assigned specific elements in the TEI scheme.
3.17.1.6. The Source Description
The <sourceDesc> is a mandatory element which records details of the source or sources from which the computer file is derived. It may contain simple prose or a bibliographic citation, using one or more of the following elements:
- bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
- listBibl (citation list) contains a list of bibliographic citations of any kind.
Examples:
<sourceDesc>
<bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)</bibl>
</sourceDesc>
<sourceDesc>
<bibl>
<author>CNN Network News</author>
<title>News headlines</title>
<date>12 Jun
1989</date>
</bibl>
</sourceDesc>
3.17.2. The Encoding Description
The <encodingDesc> element specifies the methods and editorial principles which governed the transcription of the text. Its use is highly recommended. It may be prose description or may contain elements from the following list:
- projectDesc (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected.
- samplingDecl (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection.
- editorialDecl (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text.
- refsDecl (references declaration) specifies how canonical references are constructed for this text.
- classDecl (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text.
3.17.2.1. Project and Sampling Descriptions
Examples of <projectDesc> and <samplingDesc>:
<encodingDesc>
<projectDesc>
<p>Texts collected for
use in the Claremont Shakespeare Clinic, June 1990.
</p>
</projectDesc>
</encodingDesc>
<encodingDesc>
<samplingDecl>
<p>Samples of
2000 words taken from the beginning of the text</p>
</samplingDecl>
</encodingDesc>
3.17.2.2. Editorial Declarations
The <editorialDecl> contains a prose description of the practices used when encoding the text. Typically this description should cover such topics as the following, each of which may conveniently be given as a separate paragraph.
- correction
- how and under what circumstances corrections have been made in the text.
- normalization
- the extent to which the original source has been regularized or normalized.
- quotation
- what has been done with quotation marks in the original -- have they been retained or replaced by entity references, are opening and closing quotes distinguished, etc.
- hyphenation
- what has been done with hyphens (especially end-of-line hyphens) in the original -- have they been retained, replaced by entity references, etc.
- segmentation
- how has the text has been segmented, for example into sentences, tone-units, graphemic strata, etc.
- interpretation
- what analytic or interpretive information has been added to the text.
Example:
<editorialDecl>
<p>The part of
speech analysis applied throughout section 4 was added by hand and has not been
checked.</p>
<p>Errors in transcription controlled by using the WordPerfect spelling
checker.</p>
<p>All words converted to Modern American spelling using Webster's 9th
Collegiate dictionary.</p>
</editorialDecl>
3.17.2.3. Reference and Classification Declarations
The <refsDecl> element is used to document the way in which any standard referencing scheme built into the encoding works. In its simplest form, it consists of prose description.
Example:
<refsDecl>
<p>The <att>n</att>
attribute on each <gi>div</gi> contains the canonical reference for each division in the
form XX.yyy where XX is the book number in roman numeral and yyy is the section number in
arabic.</p>
<p>Milestone tags refer to the edition of 1830 as E30 and that of 1850 as E50.
</p>
</refsDecl>
The <classDecl> element groups together definitions or sources for any descriptive classification schemes used by other parts of the header. At least one such scheme must be provided, encoded using the following elements:
- taxonomy defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy.
- bibl (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged.
- category contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy.
- catDesc (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal textDesc.
In the simplest case, the taxonomy may be defined by a bibliographic reference, as in the following example:
<classDecl>
<taxonomy xml:id="LC-SH">
<bibl>Library of Congress Subject Headings
</bibl>
</taxonomy>
</classDecl>
Alternatively, or in addition, the encoder may define a special purpose classification scheme, as in the following example:
<taxonomy xml:id="B">
<bibl>Brown Corpus</bibl>
<category xml:id="B.A">
<catDesc>Press
Reportage</catDesc>
<category xml:id="B.A1">
<catDesc>Daily</catDesc>
</category>
<category xml:id="B.A2">
<catDesc>Sunday</catDesc>
</category>
<category xml:id="B.A3">
<catDesc>National</catDesc>
</category>
<category xml:id="B.A4">
<catDesc>Provincial</catDesc>
</category>
<category xml:id="B.A5">
<catDesc>Political</catDesc>
</category>
<category xml:id="B.A6">
<catDesc>Sports</catDesc>
</category>
</category>
<category xml:id="B.D">
<catDesc>Religion</catDesc>
<category xml:id="B.D1">
<catDesc>Books</catDesc>
</category>
<category xml:id="B.D2">
<catDesc>Periodicals and
tracts</catDesc>
</category>
</category>
</taxonomy>
Linkage between a particular text and a category within such a taxonomy is made by means of the <catRef/> element within the <textClass> element, as described in the next section below.
3.17.3. The Profile Description
The <profileDesc> element enables information characterizing various descriptive aspects of a text to be recorded within a single framework. It has three optional components:
- creation contains information about the creation of a text.
- langUsage (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text.
- textClass (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc.
The <creation> element is useful for documenting where a work was created, even though it may not have been published or recorded there.
Example:
<creation>
<date when="1992-08">August 1992</date>
<name type="place">Taos, New Mexico</name>
</creation>
The <langUsage> element is useful where a text contains many different languages. It may contain <language> elements to document each particular language used:
- language characterizes a single language or sublanguage used within a text.
<langUsage>
<language ident="fr-CA" usage="60">Québecois</language>
<language ident="en-CA" usage="20">Canadian business English</language>
<language ident="en-GB" usage="20">British English</language>
</langUsage>
The <textClass> element classifies a text. This may be done with reference to a classification system locally defined by means of the <classDecl> element, or by reference to some externally defined established scheme such as the Universal Decimal Classification. Texts may also be classified using lists of keywords, which may themselves be drawn from locally or externally defined control lists. The following elements are used to supply such classifications:
- classCode (classification code) contains the classification code used for this text in some standard classification system.
- catRef/ (category reference) specifies one or more defined categories within some taxonomy or text typology.
- keywords contains a list of keywords or phrases identifying the topic or nature of a text.
The simplest way of classifying a text is by means of the <classCode> element. For example, a text with classification 410 in the Universal Decimal Classification might be documented as follows:
<classCode scheme="http://www.udc.org">410</classCode>
When a classification scheme has been locally defined using the <taxonomy> element discussed in the preceding subsection, the <catRef/> element should be used to reference it. To continue the earlier example, a work classified in the Brown Corpus as
Press reportage - Sunday and also as Religion might be documented as follows: <catRef target="#B.A3 #B.D"/>
The element <keywords> contains a list of keywords or phrases identifying the topic or nature of a text. As usual, the attribute scheme identifies the source from which these terms are taken. For example, if the LC Subject Headings are used, following declaration of that classification system in a <taxonomy> element as above :
<textClass>
<keywords scheme="#LCSH">
<list>
<item>English literature -- History and criticism -- Data processing.</item>
<item>English literature -- History and criticism -- Theory etc.</item>
<item>English language -- Style -- Data processing.</item>
</list>
</keywords>
</textClass>
Multiple classifications may be supplied using any of the mechanisms described in this section.
3.17.4. The Revision Description
The <revisionDesc> element provides a change log in which each change made to a text may be recorded. The log may be recorded as a sequence of <change> elements each of which contains a brief description of the change. The attributes when and who may be used to identify when the change was carried out and the agency responsible for it.
Example:
<revisionDesc>
<change when="1991-03-06" who="#EMB">File format updated</change>
<change when="1990-05-25" who="#EMB">Stuart's corrections entered</change>
</revisionDesc>
In a production environment it will usually be found preferable to use some kind of automated system to track and record changes. Many such version control systems, as they are known, can also be configured to update the TEI Header of a file automatically.
4. A Short Tour of the Processing Model
The key feature of the Processing Model is a notation that allows each element to be assigned to a structural category, which in turn is mapped to a description of how to render it. This allows a processor to know whether to handle the element or not, and broadly speaking how to display or otherwise process it. Several projects that have used TEI Simple and its Processing Model report that it cuts the length of required code by two thirds, reduces its complexity, and makes it easier to maintain. The model and rendition instructions are part of the TEI ODD and can be customized.
ODD, short for ‘One Document Does it all’, is the technology used by the TEI for maintaining its rules. An ODD is an XML document written in a literate programming style, mixing code and explanatory prose. From an ODD and with the use of an ODD Processor you can produce reference documentation as well as schemas. Support for the Processing Model is a significant extension of the TEI ODD and provides and answer to the question of what to do with a text once you have encoded it. Encoding is often the easy part. For a fuller account of ODD see the chapter on Documentation Elements in the Guidelines.
In principle there are a variety of ways in which a processor can use processing instructions encoded in the ODD to produce a readable text, whether a Web page, an epub, or a PDF. In practice Wolfgang Meier's XQuery based ODD processor is the fullest and most thoroughly tested current implementation. From the instructions in the ODD it creates an XQuery Library module that relies heavily on XQuery's typeswitch, a switch or case statement whose structure lends itself to transforming each processing instruction in the ODD into an XQuery function. In a second step the XQuery Library module is used to transform the TEI Simple text.
4.1. The <model> element with some of its attributes and children
In the TEI ODD, the specifications for a particular element are recorded in an element called <elementSpec>. The processing instructions for each element are kept in one or more <model > elements that are children of <elementSpec>. In the simplest and modal case the processing instruction is recorded as the value of a behaviour attribute:
<elementSpec ident="back" mode="change">
<model behaviour="block"/>
</elementSpec>
This means ‘Apply the behaviour block to the element <back>’.A slightly more complex processing instruction says that the rendering of the source document should be followed but specifies a rendition if there is nothing in the source:
<elementSpec ident="l" mode="change">
<model behaviour="block"
useSourceRendition="true">
<outputRendition> margin-left: 1em; </outputRendition>
</model>
</elementSpec>
The behaviour of an element may depend on its attributes or place in the XML hierarchy. Here is the processing rule that distinguishes between a header row and an ordinary row in a table:
<elementSpec ident="row" mode="change">
<model predicate="@role='label'"
behaviour="row">
<outputRendition>font-weight: bold;</outputRendition>
</model>
<model behaviour="row">
<desc>Insert table row. </desc>
</model>
</elementSpec>
The first <model> with its predicate attribute specifies the condition under which you use bold type for text in a table row. The second model specifies the default behaviour. The <desc> element in the second model explains the meaning of row behaviour. It is optional. The next example shows the different treatment of <div>, depending on whether it contains a title-page, is a child element of <front>, <body>, or <back>, or a child element of <div>: <elementSpec ident="div" mode="change">
<model predicate="@type='title_page'"
behaviour="block">
<outputRendition>border: 1px solid black; padding: 5px;</outputRendition>
</model>
<model behaviour="section"
predicate="parent::body or parent::front or parent::back"/>
<model behaviour="block"/>
</elementSpec>
The <param> child of <model> associates a behaviour with the parameters or objects to which it applies. Thus the processing instruction for <list> tells you that the behaviour list targets items:
<elementSpec ident="list" mode="change">
<model predicate="@rendition"
behaviour="list" useSourceRendition="true">
<param name="content">item</param>
</model>
<model predicate="not(@rendition)"
behaviour="list">
<param name="content">item</param>
</model>
</elementSpec>
4.2. More about Behaviours
The behaviour attribute has 26 different values, each of them describing what needs to be done to a TEI element for it to be transformed into part of a Web document, PDF file,or other output. We list them below, together with the names of the elements to which they apply, in descending order of the number of elements with which they are associated:
- INLINE (49) creates inline element out of content if there's something in <outputRendition>, use that formatting; otherwise just show text of selected content.: abbr, actor, add, am author, bibl, c, choice, corr, date, del, desc, docAuthor, docDate, docEdition, docImprint, ex, expan, figDesc, figure, foreign, formula, formula, gap, handShift, hi, label, measure, milestone, name, note, num, orig, pc, ref, reg, rhyme, rs, s, salute, seg, sic, signed, space, subst, supplied, time, unclear, w, quote
- BLOCK (35) create a block structure: address, addrLine, argument, back, body, byline, closer, dateline, div, doctitle, epigraph, figure, floatingText, formula, front, fw, group, head, imprimatur, l, lg, listBibl, note, opener, postscript, q, quote, role, roleDesc, salute, signed, sp, speaker, titlePage, titlePart, trailer
- OMIT (10) do nothing, do not process children: author, docAuthor, docDate, docEdition, docImprint, docTitle, encodingDesc, profileDesc, publisher, pubPlace, revisionDesc
- LIST (4) create a list by following content: castGroup, castList, list, listBibl
- BREAK (3) create a line, column, or page break according to type: cb, lb, pb
- LISTITEM (3) create list item: bibl, castItem, item
- ALTERNATE (2) : create a specialized display of alternating elements for displaying the preferred version and an alternative, both at once or by some method of toggling between the two: date,choice
- PARAGRAPH (2) create a paragraph out of content.: ab, p
- ANCHOR create an anchor with ID: anchor
- BODY create the body of a document body:
- CELL create a table cell: cit
- CIT show the content, with an indication of the source: cit
- DOCUMENT start a new output document: TEI
- FIGURE make a figure with the title as caption: figure
- GLYPH show a character by looking up reference to a chardesc at the given URI: g
- GRAPHIC if url is present, uses it to display graphic, else display a placeholder image. heading: graphic
- HEADING creates a heading.: head
- INDEX generate list according to type: body
- LINKcreate hyperlink: ref
- METADATA create metadata section: teiHeader
- NOTE create an note, often out of line, depending on the value of place; could be margin, footnote, endnote, inline: note
- ROW create a table row: row
- SECTION create a new section of the output document: div
- TABLE create a table: table
- TEXT create literal text: title
- TITLE create document title: fileDesc
There are several things to be said about this list. First, the names of the behaviours as well as their explanations, will be familiar to programmers who work with texts on the Web. Secondly, there are far fewer behaviours (26) than elements.
Of the 106 elements in TEI Simple 76 have only one behaviour associated with them. Not quite two dozen elements have two behaviours associated with them. The omit behaviour is used to suppress the display of elements that can occur both in the <teiHeader> and the <text> element, as in the following example:
<elementSpec ident="docDate" mode="change">
<model predicate="ancestor::teiHeader"
behaviour="omit">
<desc>Omit if located in teiHeader. </desc>
</model>
<model behaviour="inline"/>
</elementSpec>
Because the processor moves across <model> elements in the order of their occurrence, it is important to put the more specific condition first. In the following examples the alternatives are stated with equal degrees of explicitness, and the order does not matter: <elementSpec ident="list" mode="change">
<model predicate="@rendition"
behaviour="list" useSourceRendition="true">
<param name="content">item</param>
</model>
<model predicate="not(@rendition)"
behaviour="list">
<param name="content">item</param>
</model>
</elementSpec>
Half a dozen elements have more than two models, but more does not necessarily mean more complex. Take the <head> element, which can appear in a variety of environments and for which the Processing Model enumerates five explicit cases followed by a default case:
<elementSpec ident="head" mode="change">
<model predicate="parent::figure"
behaviour="block">
<outputRendition>font-style: italic;</outputRendition>
</model>
<model predicate="parent::table"
behaviour="block">
<outputRendition>font-style: italic;</outputRendition>
</model>
<model predicate="parent::lg"
behaviour="block">
<outputRendition>font-style: italic;</outputRendition>
</model>
<model predicate="parent::list"
behaviour="block">
<outputRendition>font-weight: bold;</outputRendition>
</model>
<model predicate="parent::div"
behaviour="heading">
<param name="level">count(ancestor::div)</param>
</model>
<model behaviour="block"/>
</elementSpec>
Four of these models combine a predicate specifying the parent element with a simple CSS rendering instruction. The instruction for headings of <div> elements is a little more interesting: count(ancestor::div) is a little function that numbers the divs automatically.A few processing instructions are quite complex. Take the behaviour alternate, which allows you to toggle between two different elements that are alternative child elements of <choice> and lets you choose between
- an abbreviation and its expansion (<abbr> ad <expan>
- an error in the text and its correction (<sic> ad <corr>)
- an orthographic variant and its regular form (<orig> ad <reg>)
Two elements (<body> and <title> have processing instructions in which several model elements are chained together as a sequence and wrapped in a <modelSequence>. The processing instruction for <body> reads
<elementSpec ident="body" mode="change">
<modelSequence>
<model behaviour="index">
<param name="type">'toc'</param>
</model>
<model behaviour="block"/>
</modelSequence>
</elementSpec>
This sequence creates the framework for a display of the text together with a navigation panel that contains a table of context. The other (and rather daunting) <modelSequence> works through all the options of displaying titles in various bibliographical environments.4.3. Customizing the Processing Model
The point of the Processing Model is to reduce the time and effort it takes to publish a TEI text that meets scholarly standards. Its virtues are Spartan rather than Corinthian. If you can get acceptable results by staying within its rules you probably should. But modifications are possible and will sometimes be necessary. Some of them are easier to achieve than others. A processing instruction like
<outputRendition>font-style: italic;</outputRendition>
is just a specific form of the more general <outputRendition>{some CSS}</outputRendition>
It is not hard to replace one set of CSS instructions with another. Changing the basic behaviour of a model is a different matter, and you need to think about unintended consequences. The following figure illustrates the general workflow of the Processing Model. Red and green are used as they are in traffic signals. Traveling along the green lines will be relatively easy. The red lines may cause trouble and will certainly involve a lot more work.
5.
This method of working assumes a workflow with three parts, and three distinct roles, to create a digital edition from a TEI text:
- an editor is responsible for the encoding and makes high-level output decisions. These fall into two parts
- Structural descriptions, eg ‘should the original or corrected version be displayed by default’, or ‘is this a block level or inline component’
- Indications of appearance (‘titles are in italics’).
- a designer creates the output envelope (for example, a book layout using InDesign or a web site using Drupal), making decisions in conjunction with the editor (‘use Garamond font throughout’ or ‘every page must show the departmental logo’)
- a programmer takes the editor's specification, and the TEI text(s), and creates the input for the designer to make the output.
It is crucial to understand here that neither the designer nor the programmer need have any understanding of the semantics of TEI elements, or the structure of a TEI document. The programmer, particularly, can use the processing model rules to extract material from the TEI text in a relatively simple way. The method works for a variety of output formats, as the programmer simply has to provide implementations for a small number of functions, and understand the well-documented features of CSS. The concepts addressed by the functions (eg ‘block’ and ‘inline’) are in line with XSL FO, and HTML. Implementations of the processing model can be done in a variety or languages or environments, but any implementation must include an XPath 2.0 interpreter, as this is used in several places in the processing notation.
6. The TEI Simple schema
6.1. Elements
6.1.1. <TEI>
| <TEI> (TEI document) contains a single TEI-conformant document, containing a single TEI header, a single text, one or more members of the model.resourceLike class, or a combination of these. A series of <TEI> elements may be combined together to form a <teiCorpus> element. [4. Default Text Structure 15.1. Varieties of Composite Text] | |||||||||
| Module | textstructure | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Contained by | core: teiCorpus | ||||||||
| May contain | |||||||||
| Declaration |
element TEI
{
att.global.attributes,
attribute version { data.version }?,
( teiHeader, ( ( model.resourceLike+, text? ) | text ) )
} | ||||||||
| Schematron |
<s:ns prefix="tei"
uri="http://www.tei-c.org/ns/1.0"/>
<s:ns prefix="xs"
uri="http://www.w3.org/2001/XMLSchema"/> | ||||||||
| Schematron |
<s:ns prefix="rng"
uri="http://relaxng.org/ns/structure/1.0"/> | ||||||||
| Example | <TEI version="5.0" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>The shortest TEI Document Imaginable</title>
</titleStmt>
<publicationStmt>
<p>First published as part of TEI P2, this is the P5
version using a name space.</p>
</publicationStmt>
<sourceDesc>
<p>No source: this is an original work.</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<body>
<p>This is about the shortest TEI document imaginable.</p>
</body>
</text>
</TEI> | ||||||||
| Example | <TEI version="5.0" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>A TEI Document containing four page images </title>
</titleStmt>
<publicationStmt>
<p>Unpublished demonstration file.</p>
</publicationStmt>
<sourceDesc>
<p>No source: this is an original work.</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<facsimile>
<graphic url="page1.png"/>
<graphic url="page2.png"/>
<graphic url="page3.png"/>
<graphic url="page4.png"/>
</facsimile>
</TEI> | ||||||||
| Note | This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute. | ||||||||
6.1.2. <ab>
| <ab> (anonymous block) contains any arbitrary component-level unit of text, acting as an anonymous container for phrase or inter level elements analogous to, but without the semantic baggage of, a paragraph. [16.3. Blocks, Segments, and Anchors] | |
| Module | linking |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.declaring (@decls) att.fragmentable (@part) |
| Member of | |
| Contained by | drama: castList header: abstract application availability cRefPattern calendar change correction correspAction correspContext correspDesc editionStmt editorialDecl encodingDesc handNote hyphenation interpretation licence normalization prefixDef projectDesc publicationStmt punctuation quotation refsDecl samplingDecl scriptNote segmentation seriesStmt sourceDesc stdVals styleDefDecl typeNote namesdates: person transcr: metamark |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element ab
{
att.global.attributes,
att.typed.attributes,
att.declaring.attributes,
att.fragmentable.attributes,
macro.paraContent
} |
| Schematron |
<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(parent::tei:exemplum
|parent::tei:item |parent::tei:note |parent::tei:q
|parent::tei:quote |parent::tei:remarks |parent::tei:said
|parent::tei:sp |parent::tei:stage |parent::tei:cell
|parent::tei:figure)"> Abstract model violation: ab may not contain paragraphs or other ab elements.
</s:report> |
| Schematron |
<s:report test="ancestor::tei:l or ancestor::tei:lg"> Abstract model violation: Lines may not contain higher-level divisions such as p or ab.
</s:report> |
| Example | <div type="book" n="Genesis">
<div type="chapter" n="1">
<ab>In the beginning God created the heaven and the earth.</ab>
<ab>And the earth was without form, and void; and
darkness was upon the face of the deep. And the
spirit of God moved upon the face of the waters.</ab>
<ab>And God said, Let there be light: and there was light.</ab>
<!-- ...-->
</div>
</div> |
| Note | The <ab> element may be used at the encoder's discretion to mark any component-level elements in a text for which no other more specific appropriate markup is defined. |
6.1.3. <abbr>
| <abbr> (abbreviation) contains an abbreviation of any sort. [3.5.5. Abbreviations and Their Expansions] | |||||||||||||
| Module | core | ||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source) att.typed (type, @subtype)
| ||||||||||||
| Member of | |||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||||||
| Declaration |
element abbr
{
att.global.attributes,
att.source.attributes,
att.typed.attribute.subtype,
attribute type { data.enumerated }?,
macro.phraseSeq
} | ||||||||||||
| Example | <choice>
<expan>North Atlantic Treaty Organization</expan>
<abbr cert="low">NorATO</abbr>
<abbr cert="high">NATO</abbr>
<abbr cert="high" xml:lang="fr">OTAN</abbr>
</choice> | ||||||||||||
| Example | <choice>
<abbr>SPQR</abbr>
<expan>senatus populusque romanorum</expan>
</choice> | ||||||||||||
| Note | The <abbr> tag is not required; if appropriate, the encoder may transcribe abbreviations in the source text silently, without tagging them. If abbreviations are not transcribed directly but expanded silently, then the TEI header should so indicate. | ||||||||||||
6.1.4. <abstract>
| <abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source) |
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Declaration |
element abstract
{
att.global.attributes,
att.source.attributes,
( model.pLike | model.listLike )+
} |
| Example | <profileDesc>
<abstract resp="#LB">
<p>Good database design involves the acquisition and deployment of
skills which have a wider relevance to the educational process.
From a set of more or less instinctive rules of thumb a formal
discipline or "methodology" of database design has evolved.
Applying that methodology can be of great benefit to a very wide
range of academic subjects: it requires fundamental skills of
abstraction and generalisation and it provides a simple mechanism
whereby complex ideas and information structures can be
represented and manipulated, even without the use of a computer.
</p>
</abstract>
</profileDesc> |
| Note | The abstract for a born digital document should be located within the <front>; this element is provided for cases where no abstract is available in the original source. |
6.1.5. <actor>
| <actor> contains the name of an actor appearing within a cast list. [7.1.4. Cast Lists] | |
| Module | drama |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | drama: castItem |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element actor { att.global.attributes, macro.phraseSeq } |
| Example | <castItem>
<role>Mathias</role>
<roleDesc>the Burgomaster</roleDesc>
<actor>Mr. Henry Irving</actor>
</castItem> |
| Note | This element should be used only to mark the name of the actor as given in the source. Chapter 13. Names, Dates, People, and Places discusses ways of marking the components of names, and also of associating names with biographical information about a person. |
6.1.6. <add>
| <add> (addition) contains letters, words, or phrases inserted in the source text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.placement (@place) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element add
{
att.global.attributes,
att.transcriptional.attributes,
att.placement.attributes,
att.typed.attributes,
macro.paraContent
} |
| Example | The story I am
going to relate is true as to its main facts, and as to the
consequences <add place="above">of these facts</add> from which
this tale takes its title. |
| Note | In a diplomatic edition attempting to represent an original source, the <add> element should not be used for additions to the current TEI electronic edition made by editors or encoders. In these cases, either the <corr> or <supplied> element are recommended.In a TEI edition of a historical text with previous editorial emendations in which such additions or reconstructions are considered part of the source text, the use of <add> may be appropriate, dependent on the editorial philosophy of the project. |
6.1.7. <addSpan/>
| <addSpan/> (added span of text) marks the beginning of a longer sequence of text added by an author, scribe, annotator or corrector (see also <add>). [11.3.1.4. Additions and Deletions] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.placement (@place) att.typed (@type, @subtype) att.spanning (@spanTo) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | Empty element |
| Declaration |
element addSpan
{
att.global.attributes,
att.transcriptional.attributes,
att.placement.attributes,
att.typed.attributes,
att.spanning.attributes,
empty
} |
| Schematron |
<sch:assert test="@spanTo">The @spanTo attribute of <sch:name/> is required.</sch:assert> |
| Schematron |
<sch:assert test="@spanTo">L'attribut spanTo est requis.</sch:assert> |
| Example | <handNote xml:id="HEOL"
scribe="HelgiÓlafsson"/>
<!-- ... -->
<body>
<div>
<!-- text here -->
</div>
<addSpan n="added gathering" hand="#HEOL"
spanTo="#P025"/>
<div>
<!-- text of first added poem here -->
</div>
<div>
<!-- text of second added poem here -->
</div>
<div>
<!-- text of third added poem here -->
</div>
<div>
<!-- text of fourth added poem here -->
</div>
<anchor xml:id="P025"/>
<div>
<!-- more text here -->
</div>
</body> |
| Note | Both the beginning and the end of the added material must be marked; the beginning by the <addSpan/> element itself, the end by the spanTo attribute. |
6.1.8. <addrLine>
| <addrLine> (address line) contains one line of a postal address. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | core: address |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element addrLine { att.global.attributes, macro.phraseSeq } |
| Example | <address>
<addrLine>Computing Center, MC 135</addrLine>
<addrLine>P.O. Box 6998</addrLine>
<addrLine>Chicago, IL</addrLine>
<addrLine>60680 USA</addrLine>
</address> |
| Example | <addrLine>
<ref target="tel:+1-201-555-0123">(201) 555 0123</ref>
</addrLine> |
| Note | Addresses may be encoded either as a sequence of lines, or using any sequence of component elements from the model.addrPart class. Other non-postal forms of address, such as telephone numbers or email, should not be included within an <address> element directly but may be wrapped within an <addrLine> if they form part of the printed address in some source text. |
6.1.9. <address>
| <address> contains a postal address, for example of a publisher, an organization, or an individual. [3.5.2. Addresses 2.2.4. Publication, Distribution, Licensing, etc. 3.11.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode correspAction creation distributor edition extent funder geoDecl handNote language licence principal publicationStmt rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element address
{
att.global.attributes,
( model.global*, ( ( model.addrPart ), model.global* )+ )
} |
| Example | <address>
<street>via Marsala 24</street>
<postCode>40126</postCode>
<name>Bologna</name>
<name n="I">Italy</name>
</address> |
| Example | <address>
<addrLine>Computing Center, MC 135</addrLine>
<addrLine>P.O. Box 6998</addrLine>
<addrLine>Chicago, IL 60680</addrLine>
<addrLine>USA</addrLine>
</address> |
| Note | This element should be used for postal addresses only. Within it, the generic element <addrLine> may be used as an alternative to any of the more specialized elements available from the model.addrPart class, such as <street>, <postCode> etc. |
6.1.10. <am>
| <am> (abbreviation marker) contains a sequence of letters or signs present in an abbreviation which are omitted or replaced in the expanded form of the abbreviation. [11.3.1.2. Abbreviation and Expansion] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element am
{
att.global.attributes,
att.typed.attributes,
att.editLike.attributes,
( text | model.gLike | model.pPart.transcriptional )*
} |
| Example | do you <abbr>Mr<am>.</am>
</abbr> Jones?
|
| Example | <expan>
<abbr>Aug<am>g</am>
</abbr>
<ex>ustorum duo</ex>
</expan> |
6.1.11. <anchor/>
| <anchor/> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element. [8.4.2. Synchronization and Overlap 16.4. Correspondence and Alignment] | |
| Module | linking |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc subst supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | Empty element |
| Declaration |
element anchor { att.global.attributes, att.typed.attributes, empty } |
| Example | <s>The anchor is he<anchor xml:id="A234"/>re somewhere.</s>
<s>Help me find it.<ptr target="#A234"/>
</s> |
| Note | On this element, the global xml:id attribute must be supplied to specify an identifier for the point at which this element occurs within a document. The value used may be chosen freely provided that it is unique within the document and is a syntactically valid name. There is no requirement for values containing numbers to be in sequence. |
6.1.12. <appInfo>
| <appInfo> (application information) records information about an application which has edited the TEI file. [2.3.10. The Application Information Element] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | header: application |
| Declaration |
element appInfo { att.global.attributes, model.applicationLike+ } |
| Example | <appInfo>
<application version="1.24" ident="Xaira">
<label>XAIRA Indexer</label>
<ptr target="#P1"/>
</application>
</appInfo> |
6.1.13. <application>
| <application> provides information about an application which has acted upon the document. [2.3.10. The Application Information Element] | |||||||||||||
| Module | header | ||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to))
| ||||||||||||
| Member of | |||||||||||||
| Contained by | header: appInfo | ||||||||||||
| May contain | |||||||||||||
| Declaration |
element application
{
att.global.attributes,
att.typed.attributes,
att.datable.attributes,
attribute ident { data.name },
attribute version { data.versionNumber },
( model.labelLike+, ( model.ptrLike* | model.pLike* ) )
} | ||||||||||||
| Example | <appInfo>
<application version="1.5"
ident="ImageMarkupTool1" notAfter="2006-06-01">
<label>Image Markup Tool</label>
<ptr target="#P1"/>
<ptr target="#P2"/>
</application>
</appInfo> This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr> elements. | ||||||||||||
6.1.14. <argument>
| <argument> contains a formal list or prose description of the topics addressed by a subdivision of a text. [4.2. Elements Common to All Divisions 4.6. Title Pages] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element argument
{
att.global.attributes,
( ( model.global | model.headLike )*, ( ( model.common ), model.global* )+ )
} |
| Example | <argument>
<p>Monte Video — Maldonado — Excursion
to R Polanco — Lazo and Bolas — Partridges —
Absence of Trees — Deer — Capybara, or River Hog —
Tucutuco — Molothrus, cuckoo-like habits — Tyrant
Flycatcher — Mocking-bird — Carrion Hawks —
Tubes formed by Lightning — House struck</p>
</argument> |
| Note | Often contains either a list or a paragraph |
6.1.15. <att>
| <att> (attribute) contains the name of an attribute appearing within running text. [22. Documentation Elements] | |||||||||
| Module | tagdocs | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||
| May contain | Character data only | ||||||||
| Declaration |
element att
{
att.global.attributes,
attribute scheme { data.enumerated }?,
data.name
} | ||||||||
| Example | <p>The TEI defines several <soCalled>global</soCalled> attributes; their names include
<att>xml:id</att>, <att>rend</att>, <att>xml:lang</att>, <att>n</att>, <att>xml:space</att>,
and <att>xml:base</att>; <att scheme="XX">type</att> is not amongst them.</p> | ||||||||
| Note | A namespace prefix may be used in order to specify the scheme as an alternative to specifying it via the scheme attribute: it takes precedence | ||||||||
6.1.16. <author>
| <author> in a bibliographic reference, contains the name(s) of an author, personal or corporate, of a work; for example in the same form as that provided by a recognized bibliographic name authority. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) |
| Member of | |
| Contained by | header: editionStmt titleStmt |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element author
{
att.global.attributes,
att.naming.attributes,
macro.phraseSeq
} |
| Example | <author>British Broadcasting Corporation</author>
<author>La Fayette, Marie Madeleine Pioche de la Vergne, comtesse de (1634–1693)</author>
<author>Anonymous</author>
<author>Bill and Melinda Gates Foundation</author>
<author>
<persName>Beaumont, Francis</persName> and
<persName>John Fletcher</persName>
</author>
<author>
<orgName key="BBC">British Broadcasting
Corporation</orgName>: Radio 3 Network
</author> |
| Note | Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast. Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given. |
6.1.17. <authority>
| <authority> (release authority) supplies the name of a person or other agency responsible for making a work available, other than a publisher or distributor. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | core: monogr header: publicationStmt |
| May contain | |
| Declaration |
element authority { att.global.attributes, macro.phraseSeq.limited } |
| Example | <authority>John Smith</authority> |
6.1.18. <availability>
| <availability> supplies information about the availability of a text, for example any restrictions on its use or distribution, its copyright status, any licence applying to it, etc. [2.2.4. Publication, Distribution, Licensing, etc.] | |||||||||
| Module | header | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | header: publicationStmt | ||||||||
| May contain | |||||||||
| Declaration |
element availability
{
att.global.attributes,
attribute status { text }?,
( model.availabilityPart | model.pLike )+
} | ||||||||
| Example | <availability status="restricted">
<p>Available for academic research purposes only.</p>
</availability>
<availability status="free">
<p>In the public domain</p>
</availability>
<availability status="restricted">
<p>Available under licence from the publishers.</p>
</availability> | ||||||||
| Example | <availability>
<licence target="http://opensource.org/licenses/MIT">
<p>The MIT License
applies to this document.</p>
<p>Copyright (C) 2011 by The University of Victoria</p>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:</p>
<p>The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.</p>
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.</p>
</licence>
</availability> | ||||||||
| Note | A consistent format should be adopted | ||||||||
6.1.19. <back>
| <back> (back matter) contains any appendixes, etc. following the main part of a text. [4.7. Back Matter 4. Default Text Structure] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) |
| Contained by | textstructure: floatingText text transcr: facsimile |
| May contain | drama: castList namesdates: listPerson textstructure: argument byline closer div docAuthor docDate docEdition docImprint docTitle epigraph postscript signed titlePage titlePart trailer transcr: addSpan damageSpan fw listTranspose metamark space |
| Declaration |
element back
{
att.global.attributes,
att.declaring.attributes,
(
(
model.frontPart
| model.pLike.front
| model.pLike
| model.listLike
| model.global
)*,
(
(
(
( model.div1Like ),
( model.frontPart | model.div1Like | model.global )*
)
| (
( model.divLike ),
( model.frontPart | model.divLike | model.global )*
)
)?
),
( ( ( model.divBottomPart ), ( model.divBottomPart | model.global )* )? )
)
} |
| Example | <back>
<div1 type="appendix">
<head>The Golden Dream or, the Ingenuous Confession</head>
<p>To shew the Depravity of human Nature </p>
</div1>
<div1 type="epistle">
<head>A letter from the Printer, which he desires may be inserted</head>
<salute>Sir.</salute>
<p>I have done with your Copy, so you may return it to the Vatican, if you please </p>
</div1>
<div1 type="advert">
<head>The Books usually read by the Scholars of Mrs Two-Shoes are these and are sold at Mr
Newbery's at the Bible and Sun in St Paul's Church-yard.</head>
<list>
<item n="1">The Christmas Box, Price 1d.</item>
<item n="2">The History of Giles Gingerbread, 1d.</item>
<item n="42">A Curious Collection of Travels, selected from the Writers of all Nations,
10 Vol, Pr. bound 1l.</item>
</list>
</div1>
<div1 type="advert">
<head>
<hi rend="center">By the KING's Royal Patent,</hi> Are sold by J. NEWBERY, at the
Bible and Sun in St. Paul's Church-Yard.</head>
<list>
<item n="1">Dr. James's Powders for Fevers, the Small-Pox, Measles, Colds, &c.
2s. 6d</item>
<item n="2">Dr. Hooper's Female Pills, 1s.</item>
</list>
</div1>
</back> |
| Note | Because cultural conventions differ as to which elements are grouped as back matter and which as front matter, the content models for the <back> and <front> elements are identical. |
6.1.20. <bibl>
| <bibl> (bibliographic citation) contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element bibl
{
att.global.attributes,
att.typed.attributes,
att.sortable.attributes,
att.docStatus.attributes,
(
text
| model.gLike
| model.highlighted
| model.pPart.data
| model.pPart.edit
| model.segLike
| model.ptrLike
| model.biblPart
| model.global
)*
} |
| Schematron |
<s:assert test="child::* or child::text()[normalize-space()]"
role="ERROR"> Element "<s:name/>" may not be
empty. </s:assert> |
| Example | <bibl>Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale,
1990)</bibl> |
| Example | <bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>.
</bibl> |
| Example | <bibl type="article" subtype="book_chapter"
xml:id="carlin_2003">
<author>
<name>
<surname>Carlin</surname>
(<forename>Claire</forename>)</name>
</author>,
<title level="a">The Staging of Impotence : France’s last
congrès</title> dans
<bibl type="monogr">
<title level="m">Theatrum mundi : studies in honor of Ronald W.
Tobin</title>, éd.
<editor>
<name>
<forename>Claire</forename>
<surname>Carlin</surname>
</name>
</editor> et
<editor>
<name>
<forename>Kathleen</forename>
<surname>Wine</surname>
</name>
</editor>,
<pubPlace>Charlottesville, Va.</pubPlace>,
<publisher>Rookwood Press</publisher>,
<date when="2003">2003</date>.
</bibl>
</bibl> |
| Note | Contains phrase-level elements, together with any combination of elements from the biblPart class |
6.1.21. <biblFull>
| <biblFull> (fully-structured bibliographic citation) contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2. The File Description 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey) att.docStatus (@status) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element biblFull
{
att.global.attributes,
att.sortable.attributes,
att.docStatus.attributes,
(
(
titleStmt,
editionStmt?,
extent?,
publicationStmt,
seriesStmt?,
notesStmt?
),
sourceDesc*
)
} |
| Example | <biblFull>
<titleStmt>
<title>The Feminist Companion to Literature in English: women writers from the middle ages
to the present</title>
<author>Blain, Virginia</author>
<author>Clements, Patricia</author>
<author>Grundy, Isobel</author>
</titleStmt>
<editionStmt>
<edition>UK edition</edition>
</editionStmt>
<extent>1231 pp</extent>
<publicationStmt>
<publisher>Yale University Press</publisher>
<pubPlace>New Haven and London</pubPlace>
<date>1990</date>
</publicationStmt>
<sourceDesc>
<p>No source: this is an original work</p>
</sourceDesc>
</biblFull> |
6.1.22. <biblScope>
| <biblScope> (scope of bibliographic reference) defines the scope of a bibliographic reference, for example as a list of page numbers, or a named subdivision of a larger work. [3.11.2.5. Scopes and Ranges in Bibliographic Citations] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.citing (@unit, @from, @to) |
| Member of | |
| Contained by | header: seriesStmt |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element biblScope
{
att.global.attributes,
att.citing.attributes,
macro.phraseSeq
} |
| Example | <biblScope>pp 12–34</biblScope>
<biblScope unit="page" from="12" to="34"/>
<biblScope unit="volume">II</biblScope>
<biblScope unit="page">12</biblScope> |
| Note | When a single page is being cited, use the from and to attributes with an identical value. When no clear endpoint is provided, the from attribute should be used without to. For example, if the citation has ‘p. 3ff’ as a page reference. |
6.1.23. <biblStruct>
| <biblStruct> (structured bibliographic citation) contains a structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.sortable (@sortKey) att.docStatus (@status) |
| Member of | |
| Contained by | |
| May contain | core: monogr note ref relatedItem header: idno |
| Declaration |
element biblStruct
{
att.global.attributes,
att.typed.attributes,
att.sortable.attributes,
att.docStatus.attributes,
(
analytic*,
( monogr, series* )+,
( model.noteLike | idno | model.ptrLike | relatedItem | citedRange )*
)
} |
| Schematron | The use of an <idno> element as a direct child of <biblStruct> is deprecated. Rather, <idno> should appear as a child of a <monogr>, <analytic>, or <series>.
<sch:report test="child::tei:idno"
role="nonfatal">WARNING: use of deprecated method — the use of the idno element as a direct child of the biblStruct element will be removed from the TEI on 2016-09-18</sch:report> |
| Example | <biblStruct>
<monogr>
<author>Blain, Virginia</author>
<author>Clements, Patricia</author>
<author>Grundy, Isobel</author>
<title>The Feminist Companion to Literature in English: women writers from the middle ages
to the present</title>
<edition>first edition</edition>
<imprint>
<publisher>Yale University Press</publisher>
<pubPlace>New Haven and London</pubPlace>
<date>1990</date>
</imprint>
</monogr>
</biblStruct> |
6.1.24. <body>
| <body> (text body) contains the whole body of a single unitary text, excluding any front or back matter. [4. Default Text Structure] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) |
| Contained by | textstructure: floatingText text |
| May contain | core: bibl biblStruct cb cit desc gap head l label lb lg list listBibl milestone note p pb q quote sp stage header: biblFull msdescription: msDesc namesdates: listPerson textstructure: argument byline closer dateline div docAuthor docDate epigraph floatingText opener postscript salute signed trailer transcr: addSpan damageSpan fw listTranspose metamark space |
| Declaration |
element body
{
att.global.attributes,
att.declaring.attributes,
(
model.global*,
( ( model.divTop ), ( model.global | model.divTop )* )?,
( ( model.divGenLike ), ( model.global | model.divGenLike )* )?,
(
( ( model.divLike ), ( model.global | model.divGenLike )* )+
| ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
| (
( ( model.common ), model.global* )+,
(
( ( model.divLike ), ( model.global | model.divGenLike )* )+
| ( ( model.div1Like ), ( model.global | model.divGenLike )* )+
)?
)
),
( ( model.divBottom ), model.global* )*
)
} |
6.1.25. <byline>
| <byline> contains the primary statement of responsibility given for a work on its title page or at the head or end of the work. [4.2.2. Openers and Closers 4.5. Front Matter] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno textstructure: docAuthor transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element byline
{
att.global.attributes,
( text | model.gLike | model.phrase | docAuthor | model.global )*
} |
| Example | <byline>Written by a CITIZEN who continued all the
while in London. Never made publick before.</byline> |
| Example | <byline>Written from her own MEMORANDUMS</byline> |
| Example | <byline>By George Jones, Political Editor, in Washington</byline> |
| Example | <byline>BY
<docAuthor>THOMAS PHILIPOTT,</docAuthor>
Master of Arts,
(Somtimes)
Of Clare-Hall in Cambridge.</byline> |
| Note | The byline on a title page may include either the name or a description for the document's author. Where the name is included, it may optionally be tagged using the <docAuthor> element. |
6.1.26. <c>
| <c> (character) represents a character. [17.1. Linguistic Segment Categories] | |
| Module | analysis |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.segLike (@function) (att.fragmentable (@part)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | gaiji: g |
| Declaration |
element c
{
att.global.attributes,
att.segLike.attributes,
att.typed.attributes,
macro.xtext
} |
| Example | <phr>
<c>M</c>
<c>O</c>
<c>A</c>
<c>I</c>
<w>doth</w>
<w>sway</w>
<w>my</w>
<w>life</w>
</phr> |
| Note | Contains a single character, a <g> element, or a sequence of graphemes to be treated as a single character. The type attribute is used to indicate the function of this segmentation, taking values such as letter, punctuation, or digit etc. |
6.1.27. <cRefPattern>
| <cRefPattern> (canonical reference pattern) specifies an expression and replacement pattern for transforming a canonical reference into a URI. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.patternReplacement (@matchPattern, @replacementPattern) |
| Contained by | header: refsDecl |
| May contain | |
| Declaration |
element cRefPattern
{
att.global.attributes,
att.patternReplacement.attributes,
model.pLike*
} |
| Example | <cRefPattern matchPattern="([1-9A-Za-z]+)\s+([0-9]+):([0-9]+)"
replacementPattern="#xpath(//div[@type='book'][@n='$1']/div[@type='chap'][@n='$2']/div[@type='verse'][@n='$3'])"/> |
| Note | The result of the substitution may be either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the cRef attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base. |
6.1.28. <calendar>
| <calendar> describes a calendar or dating system used in a dating formula in the text. [2.4.5. Calendar Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate) |
| Contained by | header: calendarDesc |
| May contain | |
| Declaration |
element calendar
{
att.global.attributes,
att.pointing.attributes,
model.pLike+
} |
| Example | <calendarDesc>
<calendar xml:id="Julian">
<p>Julian Calendar (including proleptic)</p>
</calendar>
</calendarDesc> |
| Example | <calendarDesc>
<calendar xml:id="Egyptian"
target="http://en.wikipedia.org/wiki/Egyptian_calendar">
<p>Egyptian calendar (as defined by Wikipedia)</p>
</calendar>
</calendarDesc> |
6.1.29. <calendarDesc>
| <calendarDesc> (calendar description) contains a description of the calendar system used in any dating expression found in the text. [2.4. The Profile Description 2.4.5. Calendar Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: profileDesc |
| May contain | header: calendar |
| Declaration |
element calendarDesc { att.global.attributes, calendar+ } |
| Example | <calendarDesc>
<calendar xml:id="cal_AD">
<p>Anno Domini (Christian Era)</p>
</calendar>
<calendar xml:id="cal_AH">
<p>Anno Hegirae (Muhammedan Era)</p>
</calendar>
<calendar xml:id="cal_AME">
<p>Mauludi Era (solar years since Mohammed's birth)</p>
</calendar>
<calendar xml:id="cal_AM">
<p>Anno Mundi (Jewish Calendar)</p>
</calendar>
<calendar xml:id="cal_AP">
<p>Anno Persici</p>
</calendar>
<calendar xml:id="cal_AS">
<p>Aji Saka Era (Java)</p>
</calendar>
<calendar xml:id="cal_BE">
<p>Buddhist Era</p>
</calendar>
<calendar xml:id="cal_CB">
<p>Cooch Behar Era</p>
</calendar>
<calendar xml:id="cal_CE">
<p>Common Era</p>
</calendar>
<calendar xml:id="cal_CL">
<p>Chinese Lunar Era</p>
</calendar>
<calendar xml:id="cal_CS">
<p>Chula Sakarat Era</p>
</calendar>
<calendar xml:id="cal_EE">
<p>Ethiopian Era</p>
</calendar>
<calendar xml:id="cal_FE">
<p>Fasli Era</p>
</calendar>
<calendar xml:id="cal_ISO">
<p>ISO 8601 calendar</p>
</calendar>
<calendar xml:id="cal_JE">
<p>Japanese Calendar</p>
</calendar>
<calendar xml:id="cal_KE">
<p>Khalsa Era (Sikh calendar)</p>
</calendar>
<calendar xml:id="cal_KY">
<p>Kali Yuga</p>
</calendar>
<calendar xml:id="cal_ME">
<p>Malabar Era</p>
</calendar>
<calendar xml:id="cal_MS">
<p>Monarchic Solar Era</p>
</calendar>
<calendar xml:id="cal_NS">
<p>Nepal Samwat Era</p>
</calendar>
<calendar xml:id="cal_OS">
<p>Old Style (Julian Calendar)</p>
</calendar>
<calendar xml:id="cal_RS">
<p>Rattanakosin (Bangkok) Era</p>
</calendar>
<calendar xml:id="cal_SE">
<p>Saka Era</p>
</calendar>
<calendar xml:id="cal_SH">
<p>Mohammedan Solar Era (Iran)</p>
</calendar>
<calendar xml:id="cal_SS">
<p>Saka Samvat</p>
</calendar>
<calendar xml:id="cal_TE">
<p>Tripurabda Era</p>
</calendar>
<calendar xml:id="cal_VE">
<p>Vikrama Era</p>
</calendar>
<calendar xml:id="cal_VS">
<p>Vikrama Samvat Era</p>
</calendar>
</calendarDesc> |
| Example | <calendarDesc>
<calendar xml:id="cal_Gregorian">
<p>Gregorian calendar</p>
</calendar>
<calendar xml:id="cal_Julian">
<p>Julian calendar</p>
</calendar>
<calendar xml:id="cal_Islamic">
<p>Islamic or Muslim (hijri) lunar calendar</p>
</calendar>
<calendar xml:id="cal_Hebrew">
<p>Hebrew or Jewish lunisolar calendar</p>
</calendar>
<calendar xml:id="cal_Revolutionary">
<p>French Revolutionary calendar</p>
</calendar>
<calendar xml:id="cal_Iranian">
<p>Iranian or Persian (Jalaali) solar calendar</p>
</calendar>
<calendar xml:id="cal_Coptic">
<p>Coptic or Alexandrian calendar</p>
</calendar>
<calendar xml:id="cal_Chinese">
<p>Chinese lunisolar calendar</p>
</calendar>
</calendarDesc> |
| Example | <calendarDesc>
<calendar xml:id="cal_Egyptian"
target="http://en.wikipedia.org/wiki/Egyptian_calendar">
<p>Egyptian calendar (as defined by Wikipedia)</p>
</calendar>
</calendarDesc> |
| Note | In the first example above, calendars and short codes for xml:ids are from W3 guidelines at http://www.w3.org/TR/xpath-functions-11/#lang-cal-country |
6.1.30. <castGroup>
| <castGroup> (cast list grouping) groups one or more individual castItem elements within a cast list. [7.1.4. Cast Lists] | |
| Module | drama |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | |
| Declaration |
element castGroup
{
att.global.attributes,
(
( model.global | model.headLike )*,
( ( castItem | castGroup | roleDesc ), model.global* )+,
( trailer, model.global* )?
)
} |
| Example | <castGroup rend="braced">
<castItem>
<role>Walter</role>
<actor>Mr Frank Hall</actor>
</castItem>
<castItem>
<role>Hans</role>
<actor>Mr F.W. Irish</actor>
</castItem>
<roleDesc>friends of Mathias</roleDesc>
</castGroup> |
| Note | The rend attribute may be used, as here, to indicate whether the grouping is indicated by a brace, whitespace, font change, etc.Note that in this example the role description ‘friends of Mathias’ is understood to apply to both roles equally. |
6.1.31. <castItem>
| <castItem> (cast list item) contains a single entry within a cast list, describing either a single role or a list of non-speaking roles. [7.1.4. Cast Lists] | |||||||||
| Module | drama | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Contained by | |||||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||
| Declaration |
element castItem
{
att.global.attributes,
attribute type { text }?,
( text | model.gLike | model.castItemPart | model.phrase | model.global )*
} | ||||||||
| Example | <castItem>
<role>Player</role>
<actor>Mr Milward</actor>
</castItem> | ||||||||
| Example | <castItem type="list">Constables, Drawer, Turnkey, etc.</castItem> | ||||||||
6.1.32. <castList>
| <castList> (cast list) contains a single cast list or dramatis personae. [7.1.4. Cast Lists 7.1. Front and Back Matter ] | |
| Module | drama |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | drama: castList textstructure: argument back body div docEdition epigraph front imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | core: bibl biblStruct cb cit desc gap head l label lb lg list listBibl milestone note p pb q quote sp stage header: biblFull msdescription: msDesc namesdates: listPerson textstructure: argument byline dateline docAuthor docDate epigraph floatingText opener salute signed transcr: addSpan damageSpan fw listTranspose metamark space |
| Declaration |
element castList
{
att.global.attributes,
(
( model.divTop | model.global )*,
( ( model.common ), model.global* )*,
( ( castItem | castGroup ), model.global* )+,
( ( model.common ), model.global* )*
)
} |
| Example | <castList>
<castGroup>
<head rend="braced">Mendicants</head>
<castItem>
<role>Aafaa</role>
<actor>Femi Johnson</actor>
</castItem>
<castItem>
<role>Blindman</role>
<actor>Femi Osofisan</actor>
</castItem>
<castItem>
<role>Goyi</role>
<actor>Wale Ogunyemi</actor>
</castItem>
<castItem>
<role>Cripple</role>
<actor>Tunji Oyelana</actor>
</castItem>
</castGroup>
<castItem>
<role>Si Bero</role>
<roleDesc>Sister to Dr Bero</roleDesc>
<actor>Deolo Adedoyin</actor>
</castItem>
<castGroup>
<head rend="braced">Two old women</head>
<castItem>
<role>Iya Agba</role>
<actor>Nguba Agolia</actor>
</castItem>
<castItem>
<role>Iya Mate</role>
<actor>Bopo George</actor>
</castItem>
</castGroup>
<castItem>
<role>Dr Bero</role>
<roleDesc>Specialist</roleDesc>
<actor>Nat Okoro</actor>
</castItem>
<castItem>
<role>Priest</role>
<actor>Gbenga Sonuga</actor>
</castItem>
<castItem>
<role>The old man</role>
<roleDesc>Bero's father</roleDesc>
<actor>Dapo Adelugba</actor>
</castItem>
</castList>
<stage type="mix">The action takes place in and around the home surgery of
Dr Bero, lately returned from the wars.</stage> |
6.1.33. <catDesc>
| <catDesc> (category description) describes some category within a taxonomy or text typology, either in the form of a brief prose description or in terms of the situational parameters used by the TEI formal textDesc. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | header: category |
| May contain | |
| Declaration |
element catDesc
{
att.global.attributes,
( text | model.limitedPhrase | model.catDescPart )*
} |
| Example | <catDesc>Prose reportage</catDesc> |
| Example | <catDesc>
<textDesc n="novel">
<channel mode="w">print; part issues</channel>
<constitution type="single"/>
<derivation type="original"/>
<domain type="art"/>
<factuality type="fiction"/>
<interaction type="none"/>
<preparedness type="prepared"/>
<purpose type="entertain" degree="high"/>
<purpose type="inform" degree="medium"/>
</textDesc>
</catDesc> |
6.1.34. <catRef/>
| <catRef/> (category reference) specifies one or more defined categories within some taxonomy or text typology. [2.4.3. The Text Classification] | |||||||
| Module | header | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate)
| ||||||
| Contained by | |||||||
| May contain | Empty element | ||||||
| Declaration |
element catRef
{
att.global.attributes,
att.pointing.attributes,
attribute scheme { data.pointer }?,
empty
} | ||||||
| Example | <catRef scheme="#myTopics"
target="#news #prov #sales2"/>
<!-- elsewhere -->
<taxonomy xml:id="myTopics">
<category xml:id="news">
<catDesc>Newspapers</catDesc>
</category>
<category xml:id="prov">
<catDesc>Provincial</catDesc>
</category>
<category xml:id="sales2">
<catDesc>Low to average annual sales</catDesc>
</category>
</taxonomy> | ||||||
| Note | The scheme attribute need be supplied only if more than one taxonomy has been declared. | ||||||
6.1.35. <category>
| <category> contains an individual descriptive category, possibly nested within a superordinate category, within a user-defined taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | |
| Declaration |
element category
{
att.global.attributes,
( ( catDesc+ | ( model.descLike | model.glossLike )* ), category* )
} |
| Example | <category xml:id="b1">
<catDesc>Prose reportage</catDesc>
</category> |
| Example | <category xml:id="b2">
<catDesc>Prose </catDesc>
<category xml:id="b11">
<catDesc>journalism</catDesc>
</category>
<category xml:id="b12">
<catDesc>fiction</catDesc>
</category>
</category> |
| Example | <category xml:id="LIT">
<catDesc xml:lang="pl">literatura piękna</catDesc>
<catDesc xml:lang="en">fiction</catDesc>
<category xml:id="LPROSE">
<catDesc xml:lang="pl">proza</catDesc>
<catDesc xml:lang="en">prose</catDesc>
</category>
<category xml:id="LPOETRY">
<catDesc xml:lang="pl">poezja</catDesc>
<catDesc xml:lang="en">poetry</catDesc>
</category>
<category xml:id="LDRAMA">
<catDesc xml:lang="pl">dramat</catDesc>
<catDesc xml:lang="en">drama</catDesc>
</category>
</category> |
6.1.36. <cb/>
| <cb/> (column break) marks the beginning of a new column of a text on a multi-column page. [3.10.3. Milestone Elements] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc subst supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | Empty element |
| Declaration |
element cb
{
att.global.attributes,
att.typed.attributes,
att.edition.attributes,
att.spanning.attributes,
att.breaking.attributes,
empty
} |
| Example | Markup of an early English dictionary printed in two columns: <pb/>
<cb n="1"/>
<entryFree>
<form>Well</form>, <sense>a Pit to hold Spring-Water</sense>:
<sense>In the Art of <hi rend="italic">War</hi>, a Depth the Miner
sinks into the Ground, to find out and disappoint the Enemies Mines,
or to prepare one</sense>.
</entryFree>
<entryFree>To <form>Welter</form>, <sense>to wallow</sense>, or
<sense>lie groveling</sense>.</entryFree>
<!-- remainder of column -->
<cb n="2"/>
<entryFree>
<form>Wey</form>, <sense>the greatest Measure for dry Things,
containing five Chaldron</sense>.
</entryFree>
<entryFree>
<form>Whale</form>, <sense>the greatest of
Sea-Fishes</sense>.
</entryFree> |
| Note | On this element, the global n attribute indicates the number or other value associated with the column which follows the point of insertion of this <cb/> element. Encoders should adopt a clear and consistent policy as to whether the numbers associated with column breaks relate to the physical sequence number of the column in the whole text, or whether columns are numbered within the page. The <cb/> element is placed at the head of the column to which it refers. |
6.1.37. <cell>
| <cell> contains one cell of a table. [14.1.1. TEI Tables] | |||||||||||
| Module | figures | ||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.tableDecoration (role, @rows, @cols)
| ||||||||||
| Contained by | figures: row | ||||||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||||
| Declaration |
element cell
{
att.global.attributes,
att.tableDecoration.attribute.rows,
att.tableDecoration.attribute.cols,
attribute role { text }?,
macro.specialPara
} | ||||||||||
| Example | <row>
<cell role="label">General conduct</cell>
<cell role="data">Not satisfactory, on account of his great unpunctuality
and inattention to duties</cell>
</row> | ||||||||||
6.1.38. <change>
| <change> documents a change or set of changes made during the production of a source document, or during the revision of an electronic file. [2.6. The Revision Description 2.4.1. Creation 11.7. Changes] | |||||||
| Module | header | ||||||
| Attributes | Attributes att.ascribed (@who) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.docStatus (@status) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
| ||||||
| Contained by | header: listChange revisionDesc | ||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||
| Declaration |
element change
{
att.ascribed.attributes,
att.datable.attributes,
att.docStatus.attributes,
att.global.attributes,
att.typed.attributes,
attribute target { list { data.pointer+ } }?,
macro.specialPara
} | ||||||
| Example | <titleStmt>
<title> ... </title>
<editor xml:id="LDB">Lou Burnard</editor>
<respStmt xml:id="BZ">
<resp>copy editing</resp>
<name>Brett Zamir</name>
</respStmt>
</titleStmt>
<!-- ... -->
<revisionDesc status="published">
<change who="#BZ" when="2008-02-02"
status="public">Finished chapter 23</change>
<change who="#BZ" when="2008-01-02"
status="draft">Finished chapter 2</change>
<change n="P2.2" when="1991-12-21"
who="#LDB">Added examples to section 3</change>
<change when="1991-11-11" who="#MSM">Deleted chapter 10</change>
</revisionDesc> | ||||||
| Example | <profileDesc>
<creation>
<listChange>
<change xml:id="DRAFT1">First draft in pencil</change>
<change xml:id="DRAFT2"
notBefore="1880-12-09">First revision, mostly
using green ink</change>
<change xml:id="DRAFT3"
notBefore="1881-02-13">Final corrections as
supplied to printer.</change>
</listChange>
</creation>
</profileDesc> | ||||||
| Note | The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented. | ||||||
6.1.39. <charDecl>
| <charDecl> (character declarations) provides information about nonstandard characters and glyphs. [5.2. Markup Constructs for Representation of Characters and Glyphs] | |
| Module | gaiji |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| Declaration |
element charDecl { att.global.attributes, ( desc?, ( char | glyph )+ ) } |
| Example | <charDecl>
<char xml:id="aENL">
<charName>LATIN LETTER ENLARGED SMALL A</charName>
<mapping type="standard">a</mapping>
</char>
</charDecl> |
6.1.40. <charProp>
| <charProp> (character property) provides a name and value for some property of the parent character or glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs] | |
| Module | gaiji |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) |
| Contained by | gaiji: glyph |
| May contain | |
| Declaration |
element charProp
{
att.global.attributes,
att.typed.attributes,
( ( unicodeName | localName ), value )
} |
| Example | <charProp>
<unicodeName>character-decomposition-mapping</unicodeName>
<value>circle</value>
</charProp>
<charProp>
<localName>daikanwa</localName>
<value>36</value>
</charProp> |
| Note | If the property is a Unicode Normative Property, then its <unicodeName> must be supplied. Otherwise, its name must be specied by means of a <localName>.At a later release, additional constraints will be defined on possible value/name combinations using Schematron rules |
6.1.41. <choice>
| <choice> groups a number of alternative encodings for the same point in a text. [3.4. Simple Editorial Changes] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element choice { att.global.attributes, ( model.choicePart | choice )* } |
| Schematron |
<s:assert test="count(*) > 1" role="ERROR"> Element
"<s:name/>" must have at least two child elements.</s:assert> |
| Schematron |
<s:assert test="(tei:corr or tei:sic or tei:expan or tei:abbr or tei:reg or tei:orig)
and ((tei:corr and tei:sic) or (tei:expan and tei:abbr) or (tei:reg
and tei:orig))"
role="ERROR"> Element "<s:name/>" must have corresponding corr/sic, expand/abbr, reg/orig </s:assert> |
| Example | An American encoding of Gulliver's Travels which retains the British spelling but also provides a version regularized to American spelling might be encoded as follows. <p>Lastly, That, upon his solemn oath to observe all the above
articles, the said man-mountain shall have a daily allowance of
meat and drink sufficient for the support of <choice>
<sic>1724</sic>
<corr>1728</corr>
</choice> of our subjects,
with free access to our royal person, and other marks of our
<choice>
<orig>favour</orig>
<reg>favor</reg>
</choice>.</p> |
| Note | Because the children of a <choice> element all represent alternative ways of encoding the same sequence, it is natural to think of them as mutually exclusive. However, there may be cases where a full representation of a text requires the alternative encodings to be considered as parallel.Note also that <choice> elements may self-nest. Where the purpose of an encoding is to record multiple witnesses of a single work, rather than to identify multiple possible encoding decisions at a given point, the <app> element and associated elements discussed in section 12.1. The Apparatus Entry, Readings, and Witnesses should be preferred. |
6.1.42. <cit>
| <cit> (cited quotation) contains a quotation from some other document, together with a bibliographic reference to its source. In a dictionary it may contain an example text with at least one occurrence of the word form, used in the sense being described, or a translation of the headword, or an example. [3.3.3. Quotation 4.3.1. Grouped Texts 9.3.5.1. Examples] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | drama: castList textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element cit
{
att.global.attributes,
att.typed.attributes,
( model.qLike | model.biblLike | model.ptrLike | model.global )+
} |
| Example | <cit>
<quote>and the breath of the whale is frequently attended with such an insupportable smell,
as to bring on disorder of the brain.</quote>
<bibl>Ulloa's South America</bibl>
</cit> |
| Example | <entry>
<form>
<orth>horrifier</orth>
</form>
<cit type="translation" xml:lang="en">
<quote>to horrify</quote>
</cit>
<cit type="example">
<quote>elle était horrifiée par la dépense</quote>
<cit type="translation" xml:lang="en">
<quote>she was horrified at the expense.</quote>
</cit>
</cit>
</entry> |
6.1.43. <classCode>
| <classCode> (classification code) contains the classification code used for this text in some standard classification system. [2.4.3. The Text Classification] | |||||||
| Module | header | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||
| Contained by | |||||||
| May contain | |||||||
| Declaration |
element classCode
{
att.global.attributes,
attribute scheme { data.pointer },
macro.phraseSeq.limited
} | ||||||
| Example | <classCode scheme="http://www.udc.org">410</classCode> | ||||||
6.1.44. <classDecl>
| <classDecl> (classification declarations) contains one or more taxonomies defining any classificatory codes used elsewhere in the text. [2.3.7. The Classification Declaration 2.3. The Encoding Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | header: taxonomy |
| Declaration |
element classDecl { att.global.attributes, taxonomy+ } |
| Example | <classDecl>
<taxonomy xml:id="LCSH">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
</classDecl>
<!-- ... -->
<textClass>
<keywords scheme="#LCSH">
<term>Political science</term>
<term>United States -- Politics and government —
Revolution, 1775-1783</term>
</keywords>
</textClass> |
6.1.45. <closer>
| <closer> groups together salutations, datelines, and similar phrases appearing as a final group at the end of a division, especially of a letter. [4.2.2. Openers and Closers 4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element closer
{
att.global.attributes,
(
text
| model.gLike
| signed
| dateline
| salute
| model.phrase
| model.global
)*
} |
| Example | <div type="letter">
<p> perhaps you will favour me with a sight of it when convenient.</p>
<closer>
<salute>I remain, &c. &c.</salute>
<signed>H. Colburn</signed>
</closer>
</div> |
| Example | <div type="chapter">
<p>
<!-- .... --> and his heart was going like mad and yes I said yes I will Yes.</p>
<closer>
<dateline>
<name type="place">Trieste-Zürich-Paris,</name>
<date>1914–1921</date>
</dateline>
</closer>
</div> |
6.1.46. <corr>
| <corr> (correction) contains the correct form of a passage apparently erroneous in the copy text. [3.4.1. Apparent Errors] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element corr
{
att.global.attributes,
att.editLike.attributes,
att.typed.attributes,
macro.paraContent
} |
| Example | If all that is desired is to call attention to the fact that the copy text has been corrected, <corr> may be used alone: I don't know,
Juan. It's so far in the past now — how <corr>can we</corr> prove
or disprove anyone's theories? |
| Example | It is also possible, using the <choice> and <sic> elements, to provide an uncorrected reading: I don't know, Juan. It's so far in the past now —
how <choice>
<sic>we can</sic>
<corr>can we</corr>
</choice> prove or
disprove anyone's theories? |
6.1.47. <correction>
| <correction> (correction principles) states how and under what circumstances corrections have been made in the text. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements] | |||||||||||||||||
| Module | header | ||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | header: editorialDecl | ||||||||||||||||
| May contain | |||||||||||||||||
| Declaration |
element correction
{
att.global.attributes,
attribute status { text }?,
attribute method { text }?,
model.pLike+
} | ||||||||||||||||
| Example | <correction>
<p>Errors in transcription controlled by using the WordPerfect spelling checker, with a user
defined dictionary of 500 extra words taken from Chambers Twentieth Century
Dictionary.</p>
</correction> | ||||||||||||||||
| Note | May be used to note the results of proof reading the text against its original, indicating (for example) whether discrepancies have been silently rectified, or recorded using the editorial tags described in section 3.4. Simple Editorial Changes. | ||||||||||||||||
6.1.48. <correspAction>
| <correspAction> contains a structured description of the place, the name of a person/organization and the date related to the sending/receiving of a message or any other action related to the correspondence [2.4.6. Correspondence Description] | |||||||||||
| Module | header | ||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey) att.typed (type, @subtype)
| ||||||||||
| Member of | |||||||||||
| Contained by | header: correspDesc | ||||||||||
| May contain | |||||||||||
| Declaration |
element correspAction
{
att.global.attributes,
att.typed.attribute.subtype,
att.sortable.attributes,
attribute type
{
"sent"
| "received"
| "transmitted"
| "redirected"
| "forwarded"
| xsd:Name
}?,
( model.correspActionPart+ | model.pLike+ )
} | ||||||||||
| Example | <correspAction type="sent">
<persName>Adelbert von Chamisso</persName>
<settlement>Vertus</settlement>
<date when="1807-01-29"/>
</correspAction> | ||||||||||
6.1.49. <correspContext>
| <correspContext> (correspondence context) provides references to preceding or following correspondence related to this piece of correspondence [2.4.6. Correspondence Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: correspDesc |
| May contain | |
| Declaration |
element correspContext { att.global.attributes, model.correspContextPart+ } |
| Example | <correspContext>
<ptr type="next" subtype="toAuthor"
target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief101VarnhagenanBoeckh"/>
<ptr type="prev" subtype="fromAuthor"
target="http://tei.ibi.hu-berlin.de/berliner-intellektuelle/manuscript?Brief103BoeckhanVarnhagen"/>
</correspContext> |
| Example | <correspContext>
<ref target="http://weber-gesamtausgabe.de/A040962"> Previous letter of
<persName>Carl Maria von Weber</persName> to
<persName>Caroline Brandt</persName>:
<date when="1816-12-30">December 30, 1816</date>
</ref>
<ref target="http://weber-gesamtausgabe.de/A041003"> Next letter of
<persName>Carl Maria von Weber</persName> to
<persName>Caroline Brandt</persName>:
<date when="1817-01-05">January 5, 1817</date>
</ref>
</correspContext> |
6.1.50. <correspDesc>
| <correspDesc> (correspondence description) contains a description of the actions related to one act of correspondence [2.4.6. Correspondence Description] | |
| Module | header |
| Attributes | Attributes att.canonical (@key, @ref) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Declaration |
element correspDesc
{
att.canonical.attributes,
att.global.attributes,
att.typed.attributes,
( model.correspDescPart+ | model.pLike+ )
} |
| Example | <correspDesc>
<correspAction type="sent">
<persName>Carl Maria von Weber</persName>
<settlement>Dresden</settlement>
<date when="1817-06-23">23 June 1817</date>
</correspAction>
<correspAction type="received">
<persName>Caroline Brandt</persName>
<settlement>Prag</settlement>
</correspAction>
<correspContext>
<ref type="prev"
target="http://www.weber-gesamtausgabe.de/A041209">Previous letter of
<persName>Carl Maria von Weber</persName>
to <persName>Caroline Brandt</persName>:
<date from="1817-06-19" to="1817-06-20">June 19/20, 1817</date>
</ref>
<ref type="next"
target="http://www.weber-gesamtausgabe.de/A041217">Next letter of
<persName>Carl Maria von Weber</persName> to
<persName>Caroline Brandt</persName>:
<date when="1817-06-27">June 27, 1817</date>
</ref>
</correspContext>
</correspDesc> |
6.1.51. <creation>
| <creation> contains information about the creation of a text. [2.4.1. Creation 2.4. The Profile Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) |
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Declaration |
element creation
{
att.global.attributes,
att.datable.attributes,
( text | model.limitedPhrase | listChange )*
} |
| Example | <creation>
<date>Before 1987</date>
</creation> |
| Example | <creation>
<date when="1988-07-10">10 July 1988</date>
</creation> |
| Note | The <creation> element may be used to record details of a text's creation, e.g. the date and place it was composed, if these are of interest.It may also contain a more structured account of the various stages or revisions associated with the evolution of a text; this should be encoded using the <listChange> element. It should not be confused with the <publicationStmt> element, which records date and place of publication. |
6.1.52. <damage>
| <damage> contains an area of damage to the text witness. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.damaged (@hand, @agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element damage
{
att.global.attributes,
att.typed.attributes,
att.damaged.attributes,
macro.paraContent
} |
| Example | <l>The Moving Finger wri<damage agent="water" group="1">es; and</damage> having writ,</l>
<l>Moves <damage agent="water" group="1">
<supplied>on: nor all your</supplied>
</damage> Piety nor Wit</l> |
| Note | Since damage to text witnesses frequently makes them harder to read, the <damage> element will often contain an <unclear> element. If the damaged area is not continuous (e.g. a stain affecting several strings of text), the group attribute may be used to group together several related <damage> elements; alternatively the <join> element may be used to indicate which <damage> and <unclear> elements are part of the same physical phenomenon.The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. |
6.1.53. <damageSpan/>
| <damageSpan/> (damaged span of text) marks the beginning of a longer sequence of text which is damaged in some way but still legible. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.damaged (@hand, @agent, @degree, @group) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) att.typed (@type, @subtype) att.spanning (@spanTo) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | Empty element |
| Declaration |
element damageSpan
{
att.global.attributes,
att.damaged.attributes,
att.typed.attributes,
att.spanning.attributes,
empty
} |
| Schematron |
<s:assert test="@spanTo">The @spanTo attribute of <s:name/> is required.</s:assert> |
| Schematron |
<s:assert test="@spanTo">L'attribut spanTo est requis.</s:assert> |
| Example | <p>Paragraph partially damaged. This is the undamaged
portion <damageSpan spanTo="#a34"/>and this the damaged
portion of the paragraph.</p>
<p>This paragraph is entirely damaged.</p>
<p>Paragraph partially damaged; in the middle of this
paragraph the damage ends and the anchor point marks
the start of the <anchor xml:id="a34"/> undamaged part of the text. ...</p> |
| Note | Both the beginning and ending of the damaged sequence must be marked: the beginning by the <damageSpan/> element, the ending by the target of the spanTo attribute: if no other element available, the <anchor/> element may be used for this purpose.The damaged text must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the <damageSpan/> element should not be used. Rather, the <gap> or <unclear> element should be employed, with the value of the reason attribute giving the cause. See further sections 11.3.3.1. Damage, Illegibility, and Supplied Text and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination. |
6.1.54. <date>
6.1.55. <dateline>
| <dateline> contains a brief description of the place, date, time, etc. of production of a letter, newspaper story, or other work, prefixed or suffixed to it as a kind of heading or trailer. [4.2.2. Openers and Closers] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno textstructure: docDate transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element dateline
{
att.global.attributes,
( text | model.gLike | model.phrase | model.global | docDate )*
} |
| Example | <dateline>Walden, this 29. of August 1592</dateline> |
| Example | <div type="chapter">
<p>
<!-- ... --> and his heart was going like mad and yes I said yes I will Yes.</p>
<closer>
<dateline>
<name type="place">Trieste-Zürich-Paris,</name>
<date>1914–1921</date>
</dateline>
</closer>
</div> |
6.1.56. <del>
| <del> (deletion) contains a letter, word, or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, or a previous annotator or corrector. [3.4.3. Additions, Deletions, and Omissions] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element del
{
att.global.attributes,
att.transcriptional.attributes,
att.typed.attributes,
macro.paraContent
} |
| Example | <l>
<del rend="overtyped">Mein</del> Frisch <del rend="overstrike" type="primary">schwebt</del>
weht der Wind
</l> |
| Example | <del rend="overstrike">
<gap reason="illegible" quantity="5"
unit="character"/>
</del> |
| Note | This element should be used for deletion of shorter sequences of text, typically single words or phrases. The <delSpan> element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.The text deleted must be at least partially legible in order for the encoder to be able to transcribe it (unless it is restored in a <supplied> tag). Illegible or lost text within a deletion may be marked using the <gap> tag to signal that text is present but has not been transcribed, or is no longer visible. Attributes on the <gap> element may be used to indicate how much text is omitted, the reason for omitting it, etc. If text is not fully legible, the <unclear> element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence in a similar way. Degrees of uncertainty over what can still be read, or whether a deletion was intended may be indicated by use of the <certainty> element (see 21. Certainty, Precision, and Responsibility). There is a clear distinction in the TEI between <del> and <surplus> on the one hand and <gap> or <unclear> on the other. <del> indicates a deletion present in the source being transcribed, which states the author's or a later scribe's intent to cancel or remove text. <surplus> indicates material present in the source being transcribed which should have been so deleted, but which is not in fact. <gap> or <unclear>, by contrast, signal an editor's or encoder's decision to omit something or their inability to read the source text. See sections 11.3.1.7. Text Omitted from or Supplied in the Transcription and 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for the relationship between these and other related elements used in detailed transcription. |
6.1.57. <desc>
| <desc> (description) contains a brief description of the object documented by its parent element, including its intended usage, purpose, or application where this is appropriate. [22.4.1. Description of Components] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.translatable (@versionDate) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: add corr del desc gap graphic head hi item l lg note orig p q quote ref reg sic stage title unclear drama: castList header: application category change handNote licence rendition scriptNote tagUsage taxonomy typeNote textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element desc
{
att.global.attributes,
att.translatable.attributes,
att.typed.attributes,
macro.limitedContent
} |
| Example | <desc>contains a brief description of the purpose and application for an element, attribute,
attribute value, class, or entity.</desc> |
| Note | TEI convention requires that this be expressed as a finite clause, begining with an active verb. |
6.1.58. <distributor>
| <distributor> supplies the name of a person or other agency responsible for the distribution of a text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: publicationStmt |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element distributor { att.global.attributes, macro.phraseSeq } |
| Example | <distributor>Oxford Text Archive</distributor>
<distributor>Redwood and Burn Ltd</distributor> |
6.1.59. <div>
| <div> (text division) contains a subdivision of the front, body, or back of a text. [4.1. Divisions of the Body] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.declaring (@decls) |
| Member of | |
| Contained by | |
| May contain | core: bibl biblStruct cb cit desc gap head l label lb lg list listBibl milestone note p pb q quote sp stage header: biblFull msdescription: msDesc namesdates: listPerson textstructure: argument byline closer dateline div docAuthor docDate epigraph floatingText opener postscript salute signed trailer transcr: addSpan damageSpan fw listTranspose metamark space |
| Declaration |
element div
{
att.global.attributes,
att.typed.attributes,
att.declaring.attributes,
(
( model.divTop | model.global )*,
(
(
( ( ( model.divLike | model.divGenLike ), model.global* )+ )
| (
( ( model.common ), model.global* )+,
( ( model.divLike | model.divGenLike ), model.global* )*
)
),
( ( model.divBottom ), model.global* )*
)?
)
} |
| Schematron |
<s:report test="ancestor::tei:l"> Abstract model violation: Lines may not contain higher-level structural elements such as div.
</s:report> |
| Schematron |
<s:report test="ancestor::tei:p or ancestor::tei:ab and not(ancestor::tei:floatingText)"> Abstract model violation: p and ab may not contain higher-level structural elements such as div.
</s:report> |
| Example | <body>
<div type="part">
<head>Fallacies of Authority</head>
<p>The subject of which is Authority in various shapes, and the object, to repress all
exercise of the reasoning faculty.</p>
<div n="1" type="chapter">
<head>The Nature of Authority</head>
<p>With reference to any proposed measures having for their object the greatest
happiness of the greatest number....</p>
<div n="1.1" type="section">
<head>Analysis of Authority</head>
<p>What on any given occasion is the legitimate weight or influence to be attached to
authority ... </p>
</div>
<div n="1.2" type="section">
<head>Appeal to Authority, in What Cases Fallacious.</head>
<p>Reference to authority is open to the charge of fallacy when... </p>
</div>
</div>
</div>
</body> |
6.1.60. <docAuthor>
| <docAuthor> (document author) contains the name of the author of the document, as given on the title page (often but not always contained in a byline). [4.6. Title Pages] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element docAuthor
{
att.global.attributes,
att.canonical.attributes,
macro.phraseSeq
} |
| Example | <titlePage>
<docTitle>
<titlePart>Travels into Several Remote Nations of the World, in Four
Parts.</titlePart>
</docTitle>
<byline> By <docAuthor>Lemuel Gulliver</docAuthor>, First a Surgeon,
and then a Captain of several Ships</byline>
</titlePage> |
| Note | The document author's name often occurs within a byline, but the <docAuthor> element may be used whether the <byline> element is used or not. It should be used only for the author(s) of the entire document, not for author(s) of any subset or part of it. (Attributions of authorship of a subset or part of the document, for example of a chapter in a textbook or an article in a newspaper, may be encoded with <byline> without <docAuthor>.) |
6.1.61. <docDate>
| <docDate> (document date) contains the date of a document, as given on a title page or in a dateline. [4.6. Title Pages] | |||||||||
| Module | textstructure | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||
| Declaration |
element docDate
{
att.global.attributes,
attribute when { data.temporal.w3c }?,
macro.phraseSeq
} | ||||||||
| Example | <docImprint>Oxford, Clarendon Press, <docDate>1987</docDate>
</docImprint> | ||||||||
| Note | Cf. the general <date> element in the core tag set. This specialized element is provided for convenience in marking and processing the date of the documents, since it is likely to require specialized handling for many applications. It should be used only for the date of the entire document, not for any subset or part of it. | ||||||||
6.1.62. <docEdition>
| <docEdition> (document edition) contains an edition statement as presented on a title page of a document. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element docEdition { att.global.attributes, macro.paraContent } |
| Example | <docEdition>The Third edition Corrected</docEdition> |
| Note | Cf. the <edition> element of bibliographic citation. As usual, the shorter name has been given to the more frequent element. |
6.1.63. <docImprint>
| <docImprint> (document imprint) contains the imprint statement (place and date of publication, publisher name), as given (usually) at the foot of a title page. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb pubPlace publisher ref reg rs sic term time title unclear gaiji: g header: idno textstructure: docDate transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element docImprint
{
att.global.attributes,
(
text
| model.gLike
| model.phrase
| pubPlace
| docDate
| publisher
| model.global
)*
} |
| Example | <docImprint>Oxford, Clarendon Press, 1987</docImprint> Imprints may be somewhat more complex: <docImprint>
<pubPlace>London</pubPlace>
Printed for <name>E. Nutt</name>,
at
<pubPlace>Royal Exchange</pubPlace>;
<name>J. Roberts</name> in
<pubPlace>wick-Lane</pubPlace>;
<name>A. Dodd</name> without
<pubPlace>Temple-Bar</pubPlace>;
and <name>J. Graves</name> in
<pubPlace>St. James's-street.</pubPlace>
<date>1722.</date>
</docImprint> |
| Note | Cf. the <imprint> element of bibliographic citations. As with title, author, and editions, the shorter name is reserved for the element likely to be used more often. |
6.1.64. <docTitle>
| <docTitle> (document title) contains the title of a document, including all its constituents, as given on a title page. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element docTitle
{
att.global.attributes,
att.canonical.attributes,
( model.global*, ( titlePart, model.global* )+ )
} |
| Example | <docTitle>
<titlePart type="main">The DUNCIAD, VARIOURVM.</titlePart>
<titlePart type="sub">WITH THE PROLEGOMENA of SCRIBLERUS.</titlePart>
</docTitle> |
6.1.65. <edition>
| <edition> describes the particularities of one edition of a text. [2.2.2. The Edition Statement] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: editionStmt |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element edition { att.global.attributes, macro.phraseSeq } |
| Example | <edition>First edition <date>Oct 1990</date>
</edition>
<edition n="S2">Students' edition</edition> |
6.1.66. <editionStmt>
| <editionStmt> (edition statement) groups information relating to one edition of a text. [2.2.2. The Edition Statement 2.2. The File Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | |
| Declaration |
element editionStmt
{
att.global.attributes,
( model.pLike+ | ( edition, model.respLike* ) )
} |
| Example | <editionStmt>
<edition n="S2">Students' edition</edition>
<respStmt>
<resp>Adapted by </resp>
<name>Elizabeth Kirk</name>
</respStmt>
</editionStmt> |
| Example | <editionStmt>
<p>First edition, <date>Michaelmas Term, 1991.</date>
</p>
</editionStmt> |
6.1.67. <editor>
| <editor> contains a secondary statement of responsibility for a bibliographic item, for example the name of an individual, institution or organization, (or of several such) acting as editor, compiler, translator, etc. [3.11.2.2. Titles, Authors, and Editors] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) |
| Member of | |
| Contained by | header: editionStmt seriesStmt titleStmt |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element editor
{
att.global.attributes,
att.naming.attributes,
macro.phraseSeq
} |
| Example | <editor>Eric Johnson</editor>
<editor role="illustrator">John Tenniel</editor> |
| Note | A consistent format should be adopted.Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names. |
6.1.68. <editorialDecl>
| <editorialDecl> (editorial practice declaration) provides details of editorial principles and practices applied during the encoding of a text. [2.3.3. The Editorial Practices Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | core: p header: correction hyphenation interpretation normalization punctuation quotation segmentation stdVals linking: ab |
| Declaration |
element editorialDecl
{
att.global.attributes,
( model.pLike | model.editorialDeclPart )+
} |
| Example | <editorialDecl>
<normalization>
<p>All words converted to Modern American spelling using
Websters 9th Collegiate dictionary
</p>
</normalization>
<quotation marks="all">
<p>All opening quotation marks converted to “ all closing
quotation marks converted to &cdq;.</p>
</quotation>
</editorialDecl> |
6.1.69. <email>
6.1.70. <encodingDesc>
| <encodingDesc> (encoding description) documents the relationship between an electronic text and the source or sources from which it was derived. [2.3. The Encoding Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: teiHeader |
| May contain | core: p gaiji: charDecl header: appInfo classDecl editorialDecl geoDecl listPrefixDef projectDesc refsDecl samplingDecl styleDefDecl tagsDecl linking: ab |
| Declaration |
element encodingDesc
{
att.global.attributes,
( ( model.encodingDescPart | model.pLike )+ )
} |
| Example | <encodingDesc>
<p>Basic encoding, capturing lexical information only. All
hyphenation, punctuation, and variant spellings normalized. No
formatting or layout information preserved.</p>
</encodingDesc> |
6.1.71. <epigraph>
| <epigraph> contains a quotation, anonymous or attributed, appearing at the start or end of a section or on a title page. [4.2.3. Arguments, Epigraphs, and Postscripts 4.2. Elements Common to All Divisions 4.6. Title Pages] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element epigraph { att.global.attributes, ( model.common | model.global )* } |
| Example | <epigraph xml:lang="la">
<cit>
<bibl>Lucret.</bibl>
<quote>
<l part="F">petere inde coronam,</l>
<l>Vnde prius nulli velarint tempora Musae.</l>
</quote>
</cit>
</epigraph> |
6.1.72. <ex>
| <ex> (editorial expansion) contains a sequence of letters added by an editor or transcriber when expanding an abbreviation. [11.3.1.2. Abbreviation and Expansion] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | gaiji: g |
| Declaration |
element ex { att.global.attributes, att.editLike.attributes, macro.xtext } |
| Example | The address is Southmoor <choice>
<expan>R<ex>oa</ex>d</expan>
<abbr>Rd</abbr>
</choice> |
6.1.73. <expan>
| <expan> (expansion) contains the expansion of an abbreviation. [3.5.5. Abbreviations and Their Expansions] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element expan
{
att.global.attributes,
att.editLike.attributes,
macro.phraseSeq
} |
| Example | The address is Southmoor <choice>
<expan>Road</expan>
<abbr>Rd</abbr>
</choice> |
| Example | <expan xml:lang="la">
<abbr>Imp</abbr>
<ex>erator</ex>
</expan> |
| Note | The content of this element should usually be a complete word or phrase. The <ex> element provided by the transcr module may be used to mark up sequences of letters supplied within such an expansion. |
6.1.74. <extent>
| <extent> describes the approximate size of a text stored on some carrier medium or of some other object, digital or non-digital, specified in any convenient units. [2.2.3. Type and Extent of File 2.2. The File Description 3.11.2.4. Imprint, Size of a Document, and Reprint Information 10.7.1. Object Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element extent { att.global.attributes, macro.phraseSeq } |
| Example | <extent>3200 sentences</extent>
<extent>between 10 and 20 Mb</extent>
<extent>ten 3.5 inch high density diskettes</extent> |
| Example | The <measure> element may be used to supplied normalised or machine tractable versions of the size or sizes concerned. <extent>
<measure unit="MiB" quantity="4.2">About four megabytes</measure>
<measure unit="pages" quantity="245">245 pages of source
material</measure>
</extent> |
6.1.75. <facsimile>
| <facsimile> contains a representation of some written source in the form of a set of images rather than as transcribed or encoded text. [11.1. Digital Facsimiles] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element facsimile
{
att.global.attributes,
att.declaring.attributes,
( front?, ( model.graphicLike | surface | surfaceGrp )+, back? )
} |
| Example | <facsimile>
<graphic url="page1.png"/>
<surface>
<graphic url="page2-highRes.png"/>
<graphic url="page2-lowRes.png"/>
</surface>
<graphic url="page3.png"/>
<graphic url="page4.png"/>
</facsimile> |
| Example | <facsimile>
<surface ulx="0" uly="0" lrx="200" lry="300">
<graphic url="Bovelles-49r.png"/>
</surface>
</facsimile> |
6.1.76. <figDesc>
| <figDesc> (description of figure) contains a brief prose description of the appearance or content of a graphic figure, for use when documenting an image without displaying it. [14.4. Specific Elements for Graphic Images] | |
| Module | figures |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | figures: figure |
| May contain | |
| Declaration |
element figDesc { att.global.attributes, macro.limitedContent } |
| Example | <figure>
<graphic url="emblem1.png"/>
<head>Emblemi d'Amore</head>
<figDesc>A pair of naked winged cupids, each holding a
flaming torch, in a rural setting.</figDesc>
</figure> |
| Note | This element is intended for use as an alternative to the content of its parent <figure> element ; for example, to display when the image is required but the equipment in use cannot display graphic images. It may also be used for indexing or documentary purposes. |
6.1.77. <figure>
6.1.78. <fileDesc>
| <fileDesc> (file description) contains a full bibliographic description of an electronic file. [2.2. The File Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | header: teiHeader |
| May contain | |
| Declaration |
element fileDesc
{
att.global.attributes,
(
(
titleStmt,
editionStmt?,
extent?,
publicationStmt,
seriesStmt?,
notesStmt?
),
sourceDesc+
)
} |
| Example | <fileDesc>
<titleStmt>
<title>The shortest possible TEI document</title>
</titleStmt>
<publicationStmt>
<p>Distributed as part of TEI P5</p>
</publicationStmt>
<sourceDesc>
<p>No print source exists: this is an original digital text</p>
</sourceDesc>
</fileDesc> |
| Note | The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived. |
6.1.79. <floatingText>
| <floatingText> contains a single text of any kind, whether unitary or composite, which interrupts the text containing it at any point and after which the surrounding text resumes. [4.3.2. Floating Texts] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.typed (@type, @subtype) |
| Member of | |
| Contained by | drama: castList textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element floatingText
{
att.global.attributes,
att.declaring.attributes,
att.typed.attributes,
(
model.global*,
( front, model.global* )?,
( body | group ),
model.global*,
( back, model.global* )?
)
} |
| Example | <body>
<div type="scene">
<sp>
<p>Hush, the players begin...</p>
</sp>
<floatingText type="pwp">
<body>
<div type="act">
<sp>
<l>In Athens our tale takes place ....</l>
</sp>
<!-- ... rest of nested act here -->
</div>
</body>
</floatingText>
<sp>
<p>Now that the play is finished ...</p>
</sp>
</div>
</body> |
| Note | A floating text has the same content as any other <text> and may thus be interrupted by another floating text, or contain a <group> of tesselated texts. |
6.1.80. <foreign>
| <foreign> identifies a word or phrase as belonging to some language other than that of the surrounding text. [3.3.2.1. Foreign Words or Expressions] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element foreign { att.global.attributes, macro.phraseSeq } |
| Example | This is
heathen Greek to you still? Your <foreign xml:lang="la">lapis
philosophicus</foreign>? |
| Note | The global xml:lang attribute should be supplied for this element to identify the language of the word or phrase marked. As elsewhere, its value should be a language tag as defined in 6.1. Language Identification.This element is intended for use only where no other element is available to mark the phrase or words concerned. The global xml:lang attribute should be used in preference to this element where it is intended to mark the language of the whole of some text element. The <distinct> element may be used to identify phrases belonging to sublanguages or registers not generally regarded as true languages. |
6.1.81. <formula>
| <formula> contains a mathematical or other formula. [14.2. Formulæ and Mathematical Expressions] | |||||||||
| Module | figures | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear gaiji: glyph textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||
| May contain | |||||||||
| Declaration |
element formula
{
att.global.attributes,
attribute notation { "TeX" | xsd:Name }?,
( text | model.graphicLike | model.hiLike )*
} | ||||||||
| Example | <formula notation="tex">$E=mc^2$</formula> | ||||||||
| Example | <formula notation="none">E=mc<hi rend="sup">2</hi>
</formula> | ||||||||
| Example | <formula notation="mathml">
<m:math>
<m:mi>E</m:mi>
<m:mo>=</m:mo>
<m:mi>m</m:mi>
<m:msup>
<m:mrow>
<m:mi>c</m:mi>
</m:mrow>
<m:mrow>
<m:mn>2</m:mn>
</m:mrow>
</m:msup>
</m:math>
</formula> | ||||||||
6.1.82. <front>
| <front> (front matter) contains any prefatory matter (headers, title page, prefaces, dedications, etc.) found at the start of a document, before the main body. [4.6. Title Pages 4. Default Text Structure] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) |
| Contained by | textstructure: floatingText text transcr: facsimile |
| May contain | drama: castList figures: figure textstructure: argument byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph postscript salute signed titlePage titlePart trailer transcr: addSpan damageSpan fw listTranspose metamark space |
| Declaration |
element front
{
att.global.attributes,
att.declaring.attributes,
(
( ( model.frontPart | model.pLike | model.pLike.front | model.global )* ),
(
(
(
model.div1Like,
( model.div1Like | model.frontPart | model.global )*
)
| (
model.divLike,
( model.divLike | model.frontPart | model.global )*
)
),
( ( ( model.divBottom ), ( model.divBottom | model.global )* )? )
)?
)
} |
| Example | <front>
<epigraph>
<quote>Nam Sibyllam quidem Cumis ego ipse oculis meis
vidi in ampulla pendere, et cum illi pueri dicerent:
<q xml:lang="gr">Σίβυλλα τί θέλεις</q>; respondebat
illa: <q xml:lang="gr">ὰποθανεῖν θέλω.</q>
</quote>
</epigraph>
<div type="dedication">
<p>For Ezra Pound <q xml:lang="it">il miglior fabbro.</q>
</p>
</div>
</front> |
| Example | <front>
<div type="dedication">
<p>To our three selves</p>
</div>
<div type="preface">
<head>Author's Note</head>
<p>All the characters in this book are purely imaginary, and if the
author has used names that may suggest a reference to living persons
she has done so inadvertently.
...</p>
</div>
</front> |
| Note | Because cultural conventions differ as to which elements are grouped as front matter and which as back matter, the content models for the <front> and <back> elements are identical. |
6.1.83. <funder>
| <funder> (funding body) specifies the name of an individual, institution, or organization responsible for the funding of a project or text. [2.2.1. The Title Statement] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) |
| Member of | |
| Contained by | header: editionStmt titleStmt |
| May contain | |
| Declaration |
element funder
{
att.global.attributes,
att.canonical.attributes,
macro.phraseSeq.limited
} |
| Example | <funder>The National Endowment for the Humanities, an independent federal agency</funder>
<funder>Directorate General XIII of the Commission of the European Communities</funder>
<funder>The Andrew W. Mellon Foundation</funder>
<funder>The Social Sciences and Humanities Research Council of Canada</funder> |
| Note | Funders provide financial support for a project; they are distinct from sponsors, who provide intellectual support and authority. |
6.1.84. <fw>
| <fw> (forme work) contains a running head (e.g. a header, footer), catchword, or similar material appearing on the current page. [11.6. Headers, Footers, and Similar Matter] | |||||||||
| Module | transcr | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.placement (@place)
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc subst supplied surface surfaceGrp surplus zone verse: rhyme | ||||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||
| Declaration |
element fw
{
att.global.attributes,
att.placement.attributes,
attribute type { data.enumerated }?,
macro.phraseSeq
} | ||||||||
| Example | <fw type="sig" place="bottom">C3</fw> | ||||||||
| Note | Where running heads are consistent throughout a chapter or section, it is usually more convenient to relate them to the chapter or section, e.g. by use of the rend attribute. The <fw> element is intended for cases where the running head changes from page to page, or where details of page layout and the internal structure of the running heads are of paramount importance. | ||||||||
6.1.85. <g>
| <g> (character or glyph) represents a glyph, or a non-standard character. [5. Characters, Glyphs, and Writing Modes] | |||||||
| Module | gaiji | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell gaiji: value msdescription: repository textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||
| May contain | Character data only | ||||||
| Declaration |
element g
{
att.global.attributes,
att.typed.attributes,
attribute ref { data.pointer }?,
text
} | ||||||
| Example | <g ref="#ctlig">ct</g> This example points to a <glyph> element with the identifier ctlig like the following: <glyph xml:id="ctlig">
<!-- here we describe the particular ct-ligature intended -->
</glyph> | ||||||
| Example | <g ref="#per-glyph">per</g> The medieval brevigraph per could similarly be considered as an individual glyph, defined in a <glyph> element with the identifier per like the following: <glyph xml:id="per-glyph">
<!-- ... -->
</glyph> | ||||||
| Note | The name g is short for gaiji, which is the Japanese term for a non-standardized character or glyph. | ||||||
6.1.86. <gap>
| <gap> indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible. [3.4.3. Additions, Deletions, and Omissions] | |||||||||||||||||||||
| Module | core | ||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc supplied surface surfaceGrp surplus zone verse: rhyme | ||||||||||||||||||||
| May contain | core: desc | ||||||||||||||||||||
| Declaration |
element gap
{
att.global.attributes,
att.editLike.attributes,
attribute reason { list { data.word+ } }?,
attribute hand { data.pointer }?,
attribute agent { data.enumerated }?,
model.descLike*
} | ||||||||||||||||||||
| Example | <gap quantity="4" unit="chars"
reason="illegible"/> | ||||||||||||||||||||
| Example | <gap quantity="1" unit="essay"
reason="sampling"/> | ||||||||||||||||||||
| Example | <del>
<gap atLeast="4" atMost="8" unit="chars"
reason="illegible"/>
</del> | ||||||||||||||||||||
| Example | <gap extent="unknown" unit="lines"
reason="lost"/> | ||||||||||||||||||||
| Note | The <gap>, <unclear>, and <del> core tag elements may be closely allied in use with the <damage> and <supplied> elements, available when using the additional tagset for transcription of primary sources. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance.The <gap> tag simply signals the editors decision to omit or inability to transcribe a span of text. Other information, such as the interpretation that text was deliberately erased or covered, should be indicated using the relevant tags, such as <del> in the case of deliberate deletion. | ||||||||||||||||||||
6.1.87. <geoDecl>
| <geoDecl> (geographic coordinates declaration) documents the notation and the datum used for geographic coordinates expressed as content of the <geo> element elsewhere within the document. [2.3.8. The Geographic Coordinates Declaration] | |||||||||
| Module | header | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | header: encodingDesc | ||||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||
| Declaration |
element geoDecl
{
att.global.attributes,
attribute datum { "WGS84" | "MGRS" | "OSGB36" | "ED50" | xsd:Name }?,
macro.phraseSeq
} | ||||||||
| Example | <geoDecl datum="OSGB36"/> | ||||||||
6.1.88. <gi>
| <gi> (element name) contains the name (generic identifier) of an element. [22. Documentation Elements 22.4.4. Element Specifications] | |||||||||
| Module | tagdocs | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||
| May contain | Character data only | ||||||||
| Declaration |
element gi
{
att.global.attributes,
attribute scheme { data.enumerated }?,
data.name
} | ||||||||
| Example | <p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the
<gi scheme="DBK">listItem</gi> element.</p> This example shows the use of both a namespace prefix and the schema attribute as alternative ways of indicating that the gi in question is not a TEI element name: in practice only one method should be adopted. | ||||||||
6.1.89. <glyph>
| <glyph> (character glyph) provides descriptive information about a character glyph. [5.2. Markup Constructs for Representation of Characters and Glyphs] | |
| Module | gaiji |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | gaiji: charDecl |
| May contain | |
| Declaration |
element glyph
{
att.global.attributes,
(
glyphName?,
model.descLike*,
charProp*,
mapping*,
figure*,
model.graphicLike*,
model.noteLike*
)
} |
| Example | <glyph xml:id="rstroke">
<glyphName>LATIN SMALL LETTER R WITH A FUNNY STROKE</glyphName>
<charProp>
<localName>entity</localName>
<value>rstroke</value>
</charProp>
<figure>
<graphic url="glyph-rstroke.png"/>
</figure>
</glyph> |
6.1.90. <glyphName>
| <glyphName> (character glyph name) contains the name of a glyph, expressed following Unicode conventions for character names. [5.2. Markup Constructs for Representation of Characters and Glyphs] | |
| Module | gaiji |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | gaiji: glyph |
| May contain | Character data only |
| Declaration |
element glyphName { att.global.attributes, text } |
| Example | <glyphName>CIRCLED IDEOGRAPH 4EBA</glyphName> |
| Note | For characters of non-ideographic scripts, a name following the conventions for Unicode names should be chosen. For ideographic scripts, an Ideographic Description Sequence (IDS) as described in Chapter 10.1 of the Unicode Standard is recommended where possible. Projects working in similar fields are recommended to coordinate and publish their list of <glyphName>s to facilitate data exchange. |
6.1.91. <graphic>
| <graphic> indicates the location of an inline graphic, illustration, or figure. [3.9. Graphics and Other Non-textual Components] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.media (@width, @height, @scale) (att.internetMedia (@mimeType)) att.resourced (@url) att.declaring (@decls) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear gaiji: glyph textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePage titlePart trailer verse: rhyme |
| May contain | core: desc |
| Declaration |
element graphic
{
att.global.attributes,
att.media.attributes,
att.resourced.attributes,
att.declaring.attributes,
model.descLike*
} |
| Example | <figure>
<graphic url="fig1.png"/>
<head>Figure One: The View from the Bridge</head>
<figDesc>A Whistleresque view showing four or five sailing boats in the foreground, and a
series of buoys strung out between them.</figDesc>
</figure> |
| Note | The mimeType attribute should be used to supply the MIME media type of the image specified by the url attribute. |
6.1.92. <group>
| <group> contains the body of a composite text, grouping together a sequence of distinct texts (or groups of such texts) which are regarded as a unit for some purpose, for example the collected works of an author, a sequence of prose essays, etc. [4. Default Text Structure 4.3.1. Grouped Texts 15.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.typed (@type, @subtype) |
| Contained by | textstructure: floatingText group text |
| May contain | |
| Declaration |
element group
{
att.global.attributes,
att.declaring.attributes,
att.typed.attributes,
(
( model.divTop | model.global )*,
( ( text | group ), ( text | group | model.global )* ),
model.divBottom*
)
} |
| Example | <text>
<!-- Section on Alexander Pope starts -->
<front>
<!-- biographical notice by editor -->
</front>
<group>
<text>
<!-- first poem -->
</text>
<text>
<!-- second poem -->
</text>
</group>
</text>
<!-- end of Pope section--> |
6.1.93. <handNote>
| <handNote> (note on hand) describes a particular style or hand distinguished within a manuscript. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope) |
| Contained by | — |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element handNote
{
att.global.attributes,
att.handFeatures.attributes,
macro.specialPara
} |
| Example | <handNote scope="sole">
<p>Written in insular
phase II half-uncial with interlinear Old English gloss in an Anglo-Saxon pointed
minuscule.</p>
</handNote> |
6.1.94. <handShift/>
| <handShift/> marks the beginning of a sequence of text written in a new hand, or the beginning of a scribal stint. [11.3.2.1. Document Hands] | |||||||||
| Module | transcr | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope) att.source (@source)
| ||||||||
| Member of | |||||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||
| May contain | Empty element | ||||||||
| Declaration |
element handShift
{
att.global.attributes,
att.handFeatures.attributes,
att.source.attributes,
attribute new { data.pointer }?,
empty
} | ||||||||
| Example | <l>When wolde the cat dwelle in his ynne</l>
<handShift medium="greenish-ink"/>
<l>And if the cattes skynne be slyk <handShift medium="black-ink"/> and gaye</l> | ||||||||
| Note | The <handShift/> element may be used either to denote a shift in the document hand (as from one scribe to another, on one writing style to another). Or, it may indicate a shift within a document hand, as a change of writing style, character or ink. Like other milestone elements, it should appear at the point of transition from some other state to the state which it describes. | ||||||||
6.1.95. <head>
| <head> (heading) contains any type of heading, for example the title of a section, or the heading of a list, glossary, manuscript description, etc. [4.2.1. Headings and Trailers] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element head
{
att.global.attributes,
att.typed.attributes,
(
text
| lg
| model.gLike
| model.phrase
| model.inter
| model.lLike
| model.global
)*
} |
| Example | The most common use for the <head> element is to mark the headings of sections. In older writings, the headings or incipits may be rather longer than usual in modern works. If a section has an explicit ending as well as a heading, it should be marked as a <trailer>, as in this example: <div1 n="I" type="book">
<head>In the name of Christ here begins the first book of the ecclesiastical history of
Georgius Florentinus, known as Gregory, Bishop of Tours.</head>
<div2 type="section">
<head>In the name of Christ here begins Book I of the history.</head>
<p>Proposing as I do ...</p>
<p>From the Passion of our Lord until the death of Saint Martin four hundred and twelve
years passed.</p>
<trailer>Here ends the first Book, which covers five thousand, five hundred and ninety-six
years from the beginning of the world down to the death of Saint Martin.</trailer>
</div2>
</div1> |
| Example | The <head> element is also used to mark headings of other units, such as lists: With a few exceptions, connectives are equally
useful in all kinds of discourse: description, narration, exposition, argument. <list rend="bulleted">
<head>Connectives</head>
<item>above</item>
<item>accordingly</item>
<item>across from</item>
<item>adjacent to</item>
<item>again</item>
<item>
<!-- ... -->
</item>
</list> |
| Note | The <head> element is used for headings at all levels; software which treats (e.g.) chapter headings, section headings, and list titles differently must determine the proper processing of a <head> element based on its structural position. A <head> occurring as the first element of a list is the title of that list; one occurring as the first element of a <div1> is the title of that chapter or section. |
6.1.96. <hi>
6.1.97. <hyphenation>
| <hyphenation> summarizes the way in which hyphenation in a source text has been treated in an encoded version of it. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements] | |||||||||
| Module | header | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | header: editorialDecl | ||||||||
| May contain | |||||||||
| Declaration |
element hyphenation
{
att.global.attributes,
attribute eol { text }?,
model.pLike+
} | ||||||||
| Example | <hyphenation eol="some">
<p>End-of-line hyphenation silently removed where appropriate</p>
</hyphenation> | ||||||||
6.1.98. <idno>
| <idno> (identifier) supplies any form of identifier used to identify some object, such as a bibliographic item, a person, a title, an organization, etc. in a standardized way. [2.2.4. Publication, Distribution, Licensing, etc. 2.2.5. The Series Statement 3.11.2.4. Imprint, Size of a Document, and Reprint Information] | |||||||
| Module | header | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
| ||||||
| Member of | |||||||
| Contained by | analysis: s core: abbr add addrLine address author bibl biblScope biblStruct corr date del desc editor email expan foreign head hi item l label measure monogr name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode correspAction creation distributor edition extent funder geoDecl handNote idno language licence principal publicationStmt rendition scriptNote seriesStmt sponsor tagUsage typeNote msdescription: msIdentifier namesdates: person textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||
| May contain | |||||||
| Declaration |
element idno
{
att.global.attributes,
att.sortable.attributes,
attribute type { data.enumerated }?,
( text | model.gLike | idno )*
} | ||||||
| Example | <idno type="ISBN">978-1-906964-22-1</idno>
<idno type="ISSN">0143-3385</idno>
<idno type="DOI">10.1000/123</idno>
<idno type="URI">http://www.worldcat.org/oclc/185922478</idno>
<idno type="URI">http://authority.nzetc.org/463/</idno>
<idno type="LT">Thomason Tract E.537(17)</idno>
<idno type="Wing">C695</idno>
<idno type="oldCat">
<g ref="#sym"/>345
</idno> In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym. | ||||||
| Note | <idno> should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on <idno> are ISBN, ISSN, DOI, and URI. | ||||||
6.1.99. <imprimatur>
| <imprimatur> contains a formal statement authorizing the publication of a work, sometimes required to appear on a title page or its verso. [4.6. Title Pages] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | textstructure: titlePage |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element imprimatur { att.global.attributes, macro.paraContent } |
| Example | <imprimatur>Licensed and entred acording to Order.</imprimatur> |
6.1.100. <imprint>
| <imprint> groups information relating to the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | core: monogr |
| May contain | |
| Declaration |
element imprint
{
att.global.attributes,
(
( classCode | catRef )*,
(
( ( model.imprintPart ) | ( model.dateLike ) ),
respStmt*,
model.global*
)+
)
} |
| Example | <imprint>
<pubPlace>Oxford</pubPlace>
<publisher>Clarendon Press</publisher>
<date>1987</date>
</imprint> |
6.1.101. <interpretation>
| <interpretation> describes the scope of any analytic or interpretive information added to the text in addition to the transcription. [2.3.3. The Editorial Practices Declaration] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: editorialDecl |
| May contain | |
| Declaration |
element interpretation { att.global.attributes, model.pLike+ } |
| Example | <interpretation>
<p>The part of speech analysis applied throughout section 4 was added by hand and has not
been checked</p>
</interpretation> |
6.1.102. <item>
| <item> contains one component of a list. [3.7. Lists 2.6. The Revision Description] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey) |
| Contained by | core: list |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element item
{
att.global.attributes,
att.sortable.attributes,
macro.specialPara
} |
| Example | <list rend="numbered">
<head>Here begin the chapter headings of Book IV</head>
<item n="4.1">The death of Queen Clotild.</item>
<item n="4.2">How King Lothar wanted to appropriate one third of the Church revenues.</item>
<item n="4.3">The wives and children of Lothar.</item>
<item n="4.4">The Counts of the Bretons.</item>
<item n="4.5">Saint Gall the Bishop.</item>
<item n="4.6">The priest Cato.</item>
<item> ...</item>
</list> |
| Note | May contain simple prose or a sequence of chunks.Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the <item> element is by definition synonymous with the use of the <label> element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the <label> element, not n. |
6.1.103. <keywords>
| <keywords> contains a list of keywords or phrases identifying the topic or nature of a text. [2.4.3. The Text Classification] | |||||||
| Module | header | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||
| Contained by | header: textClass | ||||||
| May contain | |||||||
| Declaration |
element keywords
{
att.global.attributes,
attribute scheme { data.pointer }?,
( term+ | list )
} | ||||||
| Example | <keywords scheme="http://classificationweb.net">
<term>Babbage, Charles</term>
<term>Mathematicians - Great Britain - Biography</term>
</keywords> | ||||||
| Example | <keywords>
<term>Fermented beverages</term>
<term>Central Andes</term>
<term>Schinus molle</term>
<term>Molle beer</term>
<term>Indigenous peoples</term>
<term>Ethnography</term>
<term>Archaeology</term>
</keywords> | ||||||
| Note | Each individual keyword (including compound subject headings) should be supplied as a <term> element directly within the <keywords> element. An alternative usage, in which each <term> appears within a <item> inside a <list> is permitted for backwards compatibility, but is deprecated.If no control list exists for the keywords used, then no value should be supplied for the scheme attribute. | ||||||
6.1.104. <l>
| <l> (verse line) contains a single, possibly incomplete, line of verse. [3.12.1. Core Tags for Verse 3.12. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.fragmentable (@part) |
| Member of | |
| Contained by | drama: castList header: change handNote licence scriptNote typeNote textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi label lb list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element l
{
att.global.attributes,
att.fragmentable.attributes,
( text | model.gLike | model.phrase | model.inter | model.global )*
} |
| Schematron |
<s:report test="ancestor::tei:l[not(.//tei:note//tei:l[. = current()])]"> Abstract model violation: Lines may not contain lines or lg elements.
</s:report> |
| Example | <l met="x/x/x/x/x/" real="/xx/x/x/x/">Shall I compare thee to a summer's day?</l> |
6.1.105. <label>
| <label> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary. [3.7. Lists] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.placement (@place) |
| Member of | |
| Contained by | drama: castList textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element label
{
att.global.attributes,
att.typed.attributes,
att.placement.attributes,
macro.phraseSeq
} |
| Example | Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin: <list type="gloss" xml:lang="enm">
<head xml:lang="en">Vocabulary</head>
<headLabel xml:lang="en">Middle English</headLabel>
<headItem xml:lang="en">New English</headItem>
<label>nu</label>
<item xml:lang="en">now</item>
<label>lhude</label>
<item xml:lang="en">loudly</item>
<label>bloweth</label>
<item xml:lang="en">blooms</item>
<label>med</label>
<item xml:lang="en">meadow</item>
<label>wude</label>
<item xml:lang="en">wood</item>
<label>awe</label>
<item xml:lang="en">ewe</item>
<label>lhouth</label>
<item xml:lang="en">lows</item>
<label>sterteth</label>
<item xml:lang="en">bounds, frisks (cf. <cit>
<ref>Chaucer, K.T.644</ref>
<quote>a courser, <term>sterting</term>as the fyr</quote>
</cit>
</item>
<label>verteth</label>
<item xml:lang="la">pedit</item>
<label>murie</label>
<item xml:lang="en">merrily</item>
<label>swik</label>
<item xml:lang="en">cease</item>
<label>naver</label>
<item xml:lang="en">never</item>
</list> |
| Example | Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the <label> element is synonymous with the n attribute on the <item> element: I will add two facts, which have seldom occurred
in the composition of six, or at least of five quartos. <list rend="runon" type="ordered">
<label>(1)</label>
<item>My first rough manuscript, without any intermediate copy, has been sent to the press.</item>
<label>(2) </label>
<item>Not a sheet has been seen by any human eyes, excepting those of the author and the
printer: the faults and the merits are exclusively my own.</item>
</list> |
| Example | Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon: <list type="gloss">
<label>March 1757.</label>
<item>I wrote some critical observations upon Plautus.</item>
<label>March 8th.</label>
<item>I wrote a long dissertation upon some lines of Virgil.</item>
<label>June.</label>
<item>I saw Mademoiselle Curchod — <quote xml:lang="la">Omnia vincit amor, et nos cedamus
amori.</quote>
</item>
<label>August.</label>
<item>I went to Crassy, and staid two days.</item>
</list> Note that the <label> might also appear within the <item> rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice. |
| Example | Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the <label> element appears within the <p> or <lg> element, rather than as a preceding sibling of it. <p>[...]
<lb/>& n’entrer en mauuais & mal-heu-
<lb/>ré meſnage. Or des que le conſente-
<lb/>ment des parties y eſt le mariage eſt
<lb/> arreſté, quoy que de faict il ne ſoit
<label place="margin">Puiſſance maritale
entre les Romains.</label>
<lb/> conſommé. Depuis la conſomma-
<lb/>tion du mariage la femme eſt ſoubs
<lb/> la puiſſance du mary, s’il n’eſt eſcla-
<lb/>ue ou enfant de famille : car en ce
<lb/> cas, la femme, qui a eſpouſé vn en-
<lb/>fant de famille, eſt ſous la puiſſance
[...]</p> In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it. If so desired the type attribute may be used to distinguish different categories of label. |
6.1.106. <langUsage>
| <langUsage> (language usage) describes the languages, sublanguages, registers, dialects, etc. represented within a text. [2.4.2. Language Usage 2.4. The Profile Description 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: profileDesc |
| May contain | header: language |
| Declaration |
element langUsage { att.global.attributes, language+ } |
| Example | <langUsage>
<language ident="fr-CA" usage="60">Québecois</language>
<language ident="en-CA" usage="20">Canadian business English</language>
<language ident="en-GB" usage="20">British English</language>
</langUsage> |
6.1.107. <language>
| <language> characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage] | |||||||||||||
| Module | header | ||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||||
| Contained by | header: langUsage | ||||||||||||
| May contain | |||||||||||||
| Declaration |
element language
{
att.global.attributes,
attribute ident { data.language },
attribute usage { xsd:nonNegativeInteger { maxInclusive = "100" } }?,
macro.phraseSeq.limited
} | ||||||||||||
| Example | <langUsage>
<language ident="en-US" usage="75">modern American English</language>
<language ident="i-az-Arab" usage="20">Azerbaijani in Arabic script</language>
<language ident="x-lap" usage="05">Pig Latin</language>
</langUsage> | ||||||||||||
| Note | Particularly for sublanguages, an informal prose characterization should be supplied as content for the element. | ||||||||||||
6.1.108. <lb/>
| <lb/> (line break) marks the start of a new (typographic) line in some edition or version of a text. [3.10.3. Milestone Elements 7.2.5. Speech Contents] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc subst supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | Empty element |
| Declaration |
element lb
{
att.global.attributes,
att.typed.attributes,
att.edition.attributes,
att.spanning.attributes,
att.breaking.attributes,
empty
} |
| Example | This example shows typographical line breaks within metrical lines, where they occur at different places in different editions: <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> |
| Example | This example encodes typographical line breaks as a means of preserving the visual appearance of a title page. The break attribute is used to show that the line break does not (as elsewhere) mark the start of a new word. <titlePart>
<lb/>With Additions, ne-<lb break="no"/>ver before Printed.
</titlePart> |
| Note | By convention, <lb/> elements should appear at the point in the text where a new line starts. The n attribute, if used, indicates the number or other value associated with the text between this point and the next <lb/> element, typically the sequence number of the line within the page, or other appropriate unit. This element is intended to be used for marking actual line breaks on a manuscript or printed page, at the point where they occur; it should not be used to tag structural units such as lines of verse (for which the <l> element is available) except in circumstances where structural units cannot otherwise be marked.The type attribute may be used to characterize the line break in any respect. The more specialized attributes break, ed, or edRef should be preferred when the intent is to indicate whether or not the line break is word-breaking, or to note the source from which it derives. |
6.1.109. <lg>
| <lg> (line group) contains one or more verse lines functioning as a formal unit, e.g. a stanza, refrain, verse paragraph, etc. [3.12.1. Core Tags for Verse 3.12. Passages of Verse or Drama 7.2.5. Speech Contents] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.declaring (@decls) |
| Member of | |
| Contained by | drama: castList header: change handNote licence scriptNote typeNote textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element lg
{
att.global.attributes,
att.typed.attributes,
att.declaring.attributes,
(
( model.divTop | model.global )*,
( model.lLike | model.stageLike | model.labelLike | lg ),
( model.lLike | model.stageLike | model.labelLike | model.global | lg )*,
( ( model.divBottom ), model.global* )*
)
} |
| Schematron |
<sch:assert test="count(descendant::tei:lg|descendant::tei:l|descendant::tei:gap) >
0">An lg element
must contain at least one child l, lg or gap element.</sch:assert> |
| Schematron |
<s:report test="ancestor::tei:l[not(.//tei:note//tei:lg[. = current()])]"> Abstract model violation: Lines may not contain line groups.
</s:report> |
| Example | <lg type="free">
<l>Let me be my own fool</l>
<l>of my own making, the sum of it</l>
</lg>
<lg type="free">
<l>is equivocal.</l>
<l>One says of the drunken farmer:</l>
</lg>
<lg type="free">
<l>leave him lay off it. And this is</l>
<l>the explanation.</l>
</lg> |
| Note | contains verse lines or nested line groups only, possibly prefixed by a heading. |
6.1.110. <licence>
| <licence> contains information about a licence or other legal agreement applicable to the text. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) |
| Member of | |
| Contained by | header: availability |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element licence
{
att.global.attributes,
att.pointing.attributes,
att.datable.attributes,
macro.specialPara
} |
| Example | <licence target="http://www.nzetc.org/tm/scholarly/tei-NZETC-Help.html#licensing"> Licence: Creative Commons Attribution-Share Alike 3.0 New Zealand Licence
</licence> |
| Example | <availability>
<licence target="http://creativecommons.org/licenses/by/3.0/"
notBefore="2013-01-01">
<p>The Creative Commons Attribution 3.0 Unported (CC BY 3.0) Licence
applies to this document.</p>
<p>The licence was added on January 1, 2013.</p>
</licence>
</availability> |
| Note | A <licence> element should be supplied for each licence agreement applicable to the text in question. The target attribute may be used to reference a full version of the licence. The when, notBefore, notAfter, from or to attributes may be used in combination to indicate the date or dates of applicability of the licence. |
6.1.111. <line>
| <line> contains the transcription of a topographic line in the source document [11.2.2. Embedded Transcription] | |
| Module | transcr |
| Attributes | Attributes att.typed (@type, @subtype) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element line
{
att.typed.attributes,
att.global.attributes,
att.coordinated.attributes,
( text | model.global | model.gLike | model.linePart )*
} |
| Example | <surface>
<zone>
<line>Poem</line>
<line>As in Visions of — at</line>
<line>night —</line>
<line>All sorts of fancies running through</line>
<line>the head</line>
</zone>
</surface> |
| Example | <surface>
<zone>
<line>Hope you enjoyed</line>
<line>Wales, as they
said</line>
<line>to Mrs FitzHerbert</line>
<line>Mama</line>
</zone>
<zone>
<line>Printed in England</line>
</zone>
</surface> |
| Note | This element should be used only to mark up writing which is topographically organized as a series of lines, horizontal or vertical. It should not be used to mark lines of verse (for which use <l>) nor to mark linebreaks within text which has been encoded using structural elements such as <p> (for which use <lb/>). |
6.1.112. <list>
| <list> contains any sequence of items organized as a list. [3.7. Lists] | |||||||||||||||
| Module | core | ||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey) att.typed (type, @subtype)
| ||||||||||||||
| Member of | |||||||||||||||
| Contained by | drama: castList header: abstract change handNote keywords licence rendition revisionDesc scriptNote sourceDesc tagUsage typeNote textstructure: argument back body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme | ||||||||||||||
| May contain | |||||||||||||||
| Declaration |
element list
{
att.global.attributes,
att.sortable.attributes,
att.typed.attribute.subtype,
attribute type
{
"gloss" | "index" | "instructions" | "litany" | "syllogism" | xsd:Name
}?,
(
( ( model.divTop ) | ( model.global ) )*,
(
( item, model.global* )+
| (
headLabel?,
headItem?,
( label, model.global*, item, model.global* )+
)
),
( ( model.divBottom ), model.global* )*
)
} | ||||||||||||||
| Schematron |
<sch:rule context="tei:list[@type='gloss']">
<sch:assert test="tei:label">The content of a "gloss" list should include a sequence of one or more pairs of a label element followed by an item element</sch:assert></sch:rule> | ||||||||||||||
| Example | <list rend="numbered">
<item>a butcher</item>
<item>a baker</item>
<item>a candlestick maker, with
<list rend="bulleted">
<item>rings on his fingers</item>
<item>bells on his toes</item>
</list>
</item>
</list> | ||||||||||||||
| Example | <list type="syllogism" rend="bulleted">
<item>All Cretans are liars.</item>
<item>Epimenides is a Cretan.</item>
<item>ERGO Epimenides is a liar.</item>
</list> | ||||||||||||||
| Example | <list type="litany" rend="simple">
<item>God save us from drought.</item>
<item>God save us from pestilence.</item>
<item>God save us from wickedness in high places.</item>
<item>Praise be to God.</item>
</list> | ||||||||||||||
| Example | The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939): <div1 type="section">
<head>Athelstan's Ordinance</head>
<list rend="numbered">
<item n="1">Concerning thieves. First, that no thief is to be spared who is caught with
the stolen goods, [if he is] over twelve years and [if the value of the goods is] over
eightpence.
<list rend="numbered">
<item n="1.1">And if anyone does spare one, he is to pay for the thief with his
wergild — and the thief is to be no nearer a settlement on that account — or to
clear himself by an oath of that amount.</item>
<item n="1.2">If, however, he [the thief] wishes to defend himself or to escape, he is
not to be spared [whether younger or older than twelve].</item>
<item n="1.3">If a thief is put into prison, he is to be in prison 40 days, and he may
then be redeemed with 120 shillings; and the kindred are to stand surety for him
that he will desist for ever.</item>
<item n="1.4">And if he steals after that, they are to pay for him with his wergild,
or to bring him back there.</item>
<item n="1.5">And if he steals after that, they are to pay for him with his wergild,
whether to the king or to him to whom it rightly belongs; and everyone of those who
supported him is to pay 120 shillings to the king as a fine.</item>
</list>
</item>
<item n="2">Concerning lordless men. And we pronounced about these lordless men, from whom
no justice can be obtained, that one should order their kindred to fetch back such a
person to justice and to find him a lord in public meeting.
<list rend="numbered">
<item n="2.1">And if they then will not, or cannot, produce him on that appointed day,
he is then to be a fugitive afterwards, and he who encounters him is to strike him
down as a thief.</item>
<item n="2.2">And he who harbours him after that, is to pay for him with his wergild
or to clear himself by an oath of that amount.</item>
</list>
</item>
<item n="3">Concerning the refusal of justice. The lord who refuses justice and upholds
his guilty man, so that the king is appealed to, is to repay the value of the goods and
120 shillings to the king; and he who appeals to the king before he demands justice as
often as he ought, is to pay the same fine as the other would have done, if he had
refused him justice.
<list rend="numbered">
<item n="3.1">And the lord who is an accessory to a theft by his slave, and it becomes
known about him, is to forfeit the slave and be liable to his wergild on the first
occasionp if he does it more often, he is to be liable to pay all that he owns.</item>
<item n="3.2">And likewise any of the king's treasurers or of our reeves, who has been
an accessory of thieves who have committed theft, is to liable to the same.</item>
</list>
</item>
<item n="4">Concerning treachery to a lord. And we have pronounced concerning treachery to
a lord, that he [who is accused] is to forfeit his life if he cannot deny it or is
afterwards convicted at the three-fold ordeal.</item>
</list>
</div1> Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired. | ||||||||||||||
| Example | <p>These decrees, most blessed Pope Hadrian, we propounded in the public council ... and they
confirmed them in our hand in your stead with the sign of the Holy Cross, and afterwards
inscribed with a careful pen on the paper of this page, affixing thus the sign of the Holy
Cross.
<list rend="simple">
<item>I, Eanbald, by the grace of God archbishop of the holy church of York, have
subscribed to the pious and catholic validity of this document with the sign of the Holy
Cross.</item>
<item>I, Ælfwold, king of the people across the Humber, consenting have subscribed with
the sign of the Holy Cross.</item>
<item>I, Tilberht, prelate of the church of Hexham, rejoicing have subscribed with the
sign of the Holy Cross.</item>
<item>I, Higbald, bishop of the church of Lindisfarne, obeying have subscribed with the
sign of the Holy Cross.</item>
<item>I, Ethelbert, bishop of Candida Casa, suppliant, have subscribed with thef sign of
the Holy Cross.</item>
<item>I, Ealdwulf, bishop of the church of Mayo, have subscribed with devout will.</item>
<item>I, Æthelwine, bishop, have subscribed through delegates.</item>
<item>I, Sicga, patrician, have subscribed with serene mind with the sign of the Holy
Cross.</item>
</list>
</p> | ||||||||||||||
| Note | May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings. | ||||||||||||||
6.1.113. <listBibl>
| <listBibl> (citation list) contains a list of bibliographic citations of any kind. [3.11.1. Methods of Encoding Bibliographic References and Lists of References 2.2.7. The Source Description 15.3.2. Declarable Elements] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey) att.typed (@type, @subtype) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element listBibl
{
att.global.attributes,
att.sortable.attributes,
att.typed.attributes,
(
model.headLike*,
( model.biblLike | model.milestoneLike )+,
( relation | listRelation )*
)
} |
| Example | <listBibl>
<head>Works consulted</head>
<bibl>Blain, Clements and Grundy: Feminist Companion to
Literature in English (Yale, 1990)
</bibl>
<biblStruct>
<analytic>
<title>The Interesting story of the Children in the Wood</title>
</analytic>
<monogr>
<title>The Penny Histories</title>
<author>Victor E Neuberg</author>
<imprint>
<publisher>OUP</publisher>
<date>1968</date>
</imprint>
</monogr>
</biblStruct>
</listBibl> |
6.1.114. <listChange>
| <listChange> groups a number of change descriptions associated with either the creation of a source text or the revision of an encoded text. [2.6. The Revision Description 11.7. Changes] | |||||||||
| Module | header | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey)
| ||||||||
| Contained by | header: creation listChange revisionDesc | ||||||||
| May contain | header: change listChange | ||||||||
| Declaration |
element listChange
{
att.global.attributes,
att.sortable.attributes,
attribute ordered { data.truthValue }?,
( listChange | change )+
} | ||||||||
| Example | <revisionDesc>
<listChange>
<change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
<change when="1991-11-02" who="#MSM"> completed first draft </change>
</listChange>
</revisionDesc> | ||||||||
| Example | <profileDesc>
<creation>
<listChange ordered="true">
<change xml:id="CHG-1">First stage, written in ink by a writer</change>
<change xml:id="CHG-2">Second stage, written in Goethe's hand using pencil</change>
<change xml:id="CHG-3">Fixation of the revised passages and further revisions by
Goethe using ink</change>
<change xml:id="CHG-4">Addition of another stanza in a different hand,
probably at a later stage</change>
</listChange>
</creation>
</profileDesc> | ||||||||
| Note | When this element appears within the <creation> element it documents the set of revision campaigns or stages identified during the evolution of the original text. When it appears within the <revisionDesc> element, it documents only changes made during the evolution of the encoded representation of that text. | ||||||||
6.1.115. <listPerson>
| <listPerson> (list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source. [13.3.2. The Person Element 15.2. Contextual Information 2.4. The Profile Description 15.3.2. Declarable Elements] | |
| Module | namesdates |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.sortable (@sortKey) |
| Member of | |
| Contained by | drama: castList namesdates: listPerson textstructure: argument back body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | core: head namesdates: listPerson person |
| Declaration |
element listPerson
{
att.global.attributes,
att.typed.attributes,
att.sortable.attributes,
(
model.headLike*,
( model.personLike | listPerson )+,
( relation | listRelation )*
)
} |
| Example | <listPerson type="respondents">
<personGrp xml:id="PXXX"/>
<person xml:id="P1234" sex="2" age="mid"/>
<person xml:id="P4332" sex="1" age="mid"/>
<listRelation>
<relation type="personal" name="spouse"
mutual="#P1234 #P4332"/>
</listRelation>
</listPerson> |
| Note | The type attribute may be used to distinguish lists of people of a particular type if convenient. |
6.1.116. <listPrefixDef>
| <listPrefixDef> (list of prefix definitions) contains a list of definitions of prefixing schemes used in data.pointer values, showing how abbreviated URIs using each scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc listPrefixDef |
| May contain | header: listPrefixDef prefixDef |
| Declaration |
element listPrefixDef
{
att.global.attributes,
( ( prefixDef | listPrefixDef )+ )
} |
| Example | In this example, two private URI scheme prefixes are defined and patterns are provided for dereferencing them. Each prefix is also supplied with a human-readable explanation in a <p> element. <listPrefixDef>
<prefixDef ident="psn"
matchPattern="([A-Z]+)"
replacementPattern="personography.xml#$1">
<p> Private URIs using the <code>psn</code>
prefix are pointers to <gi>person</gi>
elements in the personography.xml file.
For example, <code>psn:MDH</code>
dereferences to <code>personography.xml#MDH</code>.
</p>
</prefixDef>
<prefixDef ident="bibl"
matchPattern="([a-z]+[a-z0-9]*)"
replacementPattern="http://www.example.com/getBibl.xql?id=$1">
<p> Private URIs using the <code>bibl</code> prefix can be
expanded to form URIs which retrieve the relevant
bibliographical reference from www.example.com.
</p>
</prefixDef>
</listPrefixDef> |
6.1.117. <listTranspose>
| <listTranspose> supplies a list of transpositions, each of which is indicated at some point in a document typically by means of metamarks. [11.3.4.5. Transpositions] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal profileDesc scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | transcr: transpose |
| Declaration |
element listTranspose { att.global.attributes, transpose+ } |
| Example | <listTranspose>
<transpose>
<ptr target="#ib02"/>
<ptr target="#ib01"/>
</transpose>
</listTranspose> This example might be used for a source document which indicates in some way that the elements identified by ib02 and code ib01 should be read in that order (ib02 followed by ib01), rather than in the reading order in which they are presented in the source. |
6.1.118. <localName>
| <localName> (locally-defined property name) contains a locally defined name for some property. [5.2.1. Character Properties] | |
| Module | gaiji |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | gaiji: charProp |
| May contain | Character data only |
| Declaration |
element localName { att.global.attributes, text } |
| Example | <localName>daikanwa</localName>
<localName>entity</localName> |
| Note | No definitive list of local names is proposed. However, the name entity is recommended as a means of naming the property identifying the recommended character entity name for this character or glyph. |
6.1.119. <measure>
| <measure> contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name. [3.5.3. Numbers and Measures] | |||||||
| Module | core | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.measurement (@unit, @quantity, @commodity)
| ||||||
| Member of | |||||||
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||
| Declaration |
element measure
{
att.global.attributes,
att.measurement.attributes,
attribute type { data.enumerated }?,
macro.phraseSeq
} | ||||||
| Example | <measure type="weight">
<num>2</num> pounds of flesh
</measure>
<measure type="currency">£10-11-6d</measure>
<measure type="area">2 merks of old extent</measure> | ||||||
| Example | <measure quantity="40" unit="hogshead"
commodity="rum">2 score hh rum</measure>
<measure quantity="12" unit="count"
commodity="roses">1 doz. roses</measure>
<measure quantity="1" unit="count"
commodity="tulips">a yellow tulip</measure> | ||||||
6.1.120. <metamark>
6.1.121. <milestone/>
| <milestone/> marks a boundary point separating any kind of section of a text, typically but not necessarily indicating a point at which some part of a standard reference system changes, where the change is not represented by a structural element. [3.10.3. Milestone Elements] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.milestoneUnit (@unit) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc subst supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | Empty element |
| Declaration |
element milestone
{
att.global.attributes,
att.milestoneUnit.attributes,
att.typed.attributes,
att.edition.attributes,
att.spanning.attributes,
att.breaking.attributes,
empty
} |
| Example | <milestone n="23" ed="La" unit="Dreissiger"/>
... <milestone n="24" ed="AV" unit="verse"/> ... |
| Note | For this element, the global n attribute indicates the new number or other value for the unit which changes at this milestone. The special value unnumbered should be used in passages which fall outside the normal numbering scheme, such as chapter or other headings, poem numbers or titles, etc.The order in which milestone elements are given at a given point is not normally significant. |
6.1.122. <mod>
| <mod> represents any kind of modification identified within a single document. [11.3.4.1. Generic Modification] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.typed (@type, @subtype) att.spanning (@spanTo) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element mod
{
att.global.attributes,
att.transcriptional.attributes,
att.typed.attributes,
att.spanning.attributes,
macro.paraContent
} |
| Example | <mod type="subst">
<add>pleasing</add>
<del>agreable</del>
</mod> |
6.1.123. <monogr>
| <monogr> (monographic level) contains bibliographic elements describing an item (e.g. a book or journal) published as an independent item (i.e. as a separate physical object). [3.11.2.1. Analytic, Monographic, and Series Levels] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | core: biblStruct |
| May contain | |
| Declaration |
element monogr
{
att.global.attributes,
(
(
(
( author | editor | meeting | respStmt ),
( author | editor | meeting | respStmt )*,
title+,
( model.ptrLike | idno | textLang | editor | respStmt )*
)
| (
( title | model.ptrLike | idno )+,
( textLang | author | editor | meeting | respStmt )*
)
| ( authority, idno )
)?,
availability*,
model.noteLike*,
(
edition,
( idno | model.ptrLike | editor | sponsor | funder | respStmt )*
)*,
imprint,
( imprint | extent | biblScope )*
)
} |
| Example | <biblStruct>
<analytic>
<author>Chesnutt, David</author>
<title>Historical Editions in the States</title>
</analytic>
<monogr>
<title level="j">Computers and the Humanities</title>
<imprint>
<date when="1991-12">(December, 1991):</date>
</imprint>
<biblScope>25.6</biblScope>
<biblScope unit="page" from="377" to="380">377–380</biblScope>
</monogr>
</biblStruct> |
| Example | <biblStruct type="book">
<monogr>
<author>
<persName>
<forename>Leo Joachim</forename>
<surname>Frachtenberg</surname>
</persName>
</author>
<title type="main" level="m">Lower Umpqua Texts</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Columbia University Press</publisher>
<date>1914</date>
</imprint>
</monogr>
<series>
<title type="main" level="s">Columbia University Contributions to
Anthropology</title>
<biblScope unit="volume">4</biblScope>
</series>
</biblStruct> |
| Note | May contain specialized bibliographic elements, in a prescribed order.The <monogr> element may only occur only within a <biblStruct>, where its use is mandatory for the description of a monographic-level bibliographic item. |
6.1.124. <msDesc>
| <msDesc> (manuscript description) contains a description of a single identifiable manuscript or other text-bearing object. [10.1. Overview] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.sortable (@sortKey) att.typed (@type, @subtype) att.declaring (@decls) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element msDesc
{
att.global.attributes,
att.sortable.attributes,
att.typed.attributes,
att.declaring.attributes,
(
msIdentifier,
model.headLike*,
(
model.pLike+
| ( msContents?, physDesc?, history?, additional?, msPart* )
)
)
} |
| Example | <msDesc>
<msIdentifier>
<settlement>Oxford</settlement>
<repository>Bodleian Library</repository>
<idno type="Bod">MS Poet. Rawl. D. 169.</idno>
</msIdentifier>
<msContents>
<msItem>
<author>Geoffrey Chaucer</author>
<title>The Canterbury Tales</title>
</msItem>
</msContents>
<physDesc>
<objectDesc>
<p>A parchment codex of 136 folios, measuring approx
28 by 19 inches, and containing 24 quires.</p>
<p>The pages are margined and ruled throughout.</p>
<p>Four hands have been identified in the manuscript: the first 44
folios being written in two cursive anglicana scripts, while the
remainder is for the most part in a mixed secretary hand.</p>
</objectDesc>
</physDesc>
</msDesc> |
6.1.125. <msIdentifier>
| <msIdentifier> (manuscript identifier) contains the information required to identify the manuscript being described. [10.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | header: idno msdescription: repository |
| Declaration |
element msIdentifier
{
att.global.attributes,
(
(
model.placeNamePart_sequenceOptional,
institution?,
repository?,
collection*,
idno?
),
( msName | altIdentifier )*
)
} |
| Schematron |
<s:report test="not(parent::tei:msPart) and (local-name(*[1])='idno' or
local-name(*[1])='altIdentifier' or normalize-space(.)='')">An msIdentifier must contain either a repository or location of some type, or a manuscript name</s:report> |
| Example | <msIdentifier>
<settlement>San Marino</settlement>
<repository>Huntington Library</repository>
<idno>MS.El.26.C.9</idno>
</msIdentifier> |
6.1.126. <name>
| <name> (name, proper noun) contains a proper noun or noun phrase. [3.5.1. Referring Strings] | |||||||||||
| Module | core | ||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.personal (@full, @sort) (att.naming (@role, @nymRef) (att.canonical (@key, @ref)) ) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (type, @subtype)
| ||||||||||
| Member of | |||||||||||
| Contained by | analysis: s core: abbr add addrLine address author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp respStmt rs sic speaker stage term time title unclear header: authority catDesc change classCode correspAction creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||||
| Declaration |
element name
{
att.global.attributes,
att.personal.attributes,
att.datable.attributes,
att.editLike.attributes,
att.typed.attribute.subtype,
attribute type { text }?,
macro.phraseSeq
} | ||||||||||
| Example | <name type="person">Thomas Hoccleve</name>
<name type="place">Villingaholt</name>
<name type="org">Vetus Latina Institut</name>
<name type="person" ref="#HOC001">Occleve</name> | ||||||||||
| Note | Proper nouns referring to people, places, and organizations may be tagged instead with <persName>, <placeName>, or <orgName>, when the TEI module for names and dates is included. | ||||||||||
6.1.127. <namespace>
| <namespace> supplies the formal name of the namespace to which the elements documented by its children belong. [2.3.4. The Tagging Declaration] | |||||||
| Module | header | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||
| Contained by | header: tagsDecl | ||||||
| May contain | header: tagUsage | ||||||
| Declaration |
element namespace
{
att.global.attributes,
attribute name { data.namespace },
tagUsage+
} | ||||||
| Example | <namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="hi" occurs="28" withId="2"
render="#it"> Used only to mark English words
italicized in the copy text </tagUsage>
</namespace> | ||||||
6.1.128. <normalization>
| <normalization> indicates the extent of normalization or regularization of the original source carried out in converting it to electronic form. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements] | |||||||||||||||
| Module | header | ||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||||||
| Member of | |||||||||||||||
| Contained by | header: editorialDecl | ||||||||||||||
| May contain | |||||||||||||||
| Declaration |
element normalization
{
att.global.attributes,
attribute source { data.pointer }?,
attribute method { text }?,
model.pLike+
} | ||||||||||||||
| Example | <editorialDecl>
<normalization method="markup">
<p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern
20th century typographical practice, the <gi>choice</gi> element has been used to
enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values
respectively. ... </p>
</normalization>
<normalization method="silent">
<p>Spacing between words and following punctuation has been regularized to zero spaces;
spacing between words has been regularized to one space.</p>
</normalization>
<normalization source="http://www.dict.sztaki.hu/webster">
<p>Spelling converted throughout to Modern American usage, based on Websters 9th
Collegiate dictionary.</p>
</normalization>
</editorialDecl> | ||||||||||||||
6.1.129. <note>
| <note> contains a note or annotation. [3.8.1. Notes and Simple Annotation 2.2.6. The Notes Statement 3.11.2.8. Notes and Statement of Language 9.3.5.4. Notes within Entries] | |||||||||||||||||||
| Module | core | ||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.placement (@place) att.pointing (@targetLang, @target, @evaluate) att.source (@source) att.typed (@type, @subtype)
| ||||||||||||||||||
| Member of | |||||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope biblStruct cit corr date del editor email expan foreign head hi imprint item l label lg list measure monogr name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear gaiji: glyph header: authority change classCode correspAction correspContext correspDesc distributor edition extent funder geoDecl handNote language licence notesStmt principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc supplied surface surfaceGrp surplus zone verse: rhyme | ||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||||||||||||
| Declaration |
element note
{
att.global.attributes,
att.placement.attributes,
att.pointing.attributes,
att.source.attributes,
att.typed.attributes,
attribute anchored { data.truthValue }?,
attribute targetEnd { list { data.pointer+ } }?,
macro.specialPara
} | ||||||||||||||||||
| Example | In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly": And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottom" type="gloss"
resp="#MDMH">
<term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance. For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI header:<respStmt xml:id="MDMH">
<resp>translation from German to English</resp>
<name>Hottinger, Marie Donald Mackie</name>
</respStmt> | ||||||||||||||||||
| Example | The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example: Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note n="126" anchored="true"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann. However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers. | ||||||||||||||||||
6.1.130. <notesStmt>
| <notesStmt> (notes statement) collects together any notes providing information about a text additional to that recorded in other parts of the bibliographic description. [2.2.6. The Notes Statement 2.2. The File Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | core: note relatedItem |
| Declaration |
element notesStmt { att.global.attributes, ( model.noteLike | relatedItem )+ } |
| Example | <notesStmt>
<note>Historical commentary provided by Mark Cohen</note>
<note>OCR scanning done at University of Toronto</note>
</notesStmt> |
| Note | Information of different kinds should not be grouped together into the same note. |
6.1.131. <num>
| <num> (number) contains a number, written in any form. [3.5.3. Numbers and Measures] | |||||||||||||||||||||
| Module | core | ||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.ranging (@atLeast, @atMost, @min, @max, @confidence)
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||||||||||||
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||||||||||||||
| Declaration |
element num
{
att.global.attributes,
att.ranging.attributes,
attribute type
{
"cardinal" | "ordinal" | "fraction" | "percentage" | xsd:Name
}?,
attribute value { data.numeric }?,
macro.phraseSeq
} | ||||||||||||||||||||
| Example | <p>I reached <num type="cardinal" value="21">twenty-one</num> on
my <num type="ordinal" value="21">twenty-first</num> birthday</p>
<p>Light travels at <num value="3E10">3×10<hi rend="sup">10</hi>
</num> cm per second.</p> | ||||||||||||||||||||
| Note | Detailed analyses of quantities and units of measure in historical documents may also use the feature structure mechanism described in chapter 18. Feature Structures. The <num> element is intended for use in simple applications. | ||||||||||||||||||||
6.1.132. <opener>
| <opener> groups together dateline, byline, salutation, and similar phrases appearing as a preliminary group at the start of a division, especially of a letter. [4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element opener
{
att.global.attributes,
(
text
| model.gLike
| model.phrase
| argument
| byline
| dateline
| epigraph
| salute
| signed
| model.global
)*
} |
| Example | <opener>
<dateline>Walden, this 29. of August 1592</dateline>
</opener> |
| Example | <opener>
<dateline>
<name type="place">Great Marlborough Street</name>
<date>November 11, 1848</date>
</dateline>
<salute>My dear Sir,</salute>
</opener>
<p>I am sorry to say that absence from town and other circumstances have prevented me from
earlier enquiring...</p> |
6.1.133. <orig>
| <orig> (original form) contains a reading which is marked as following the original, rather than being normalized or corrected. [3.4.2. Regularization and Normalization 12. Critical Apparatus] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element orig
{
att.global.attributes,
att.source.attributes,
macro.paraContent
} |
| Example | If all that is desired is to call attention to the original version in the copy text, <orig> may be used alone: <l>But this will be a <orig>meere</orig> confusion</l>
<l>And hardly shall we all be <orig>vnderstoode</orig>
</l> |
| Example | More usually, an <orig> will be combined with a regularized form within a <choice> element: <l>But this will be a <choice>
<orig>meere</orig>
<reg>mere</reg>
</choice> confusion</l>
<l>And hardly shall we all be <choice>
<orig>vnderstoode</orig>
<reg>understood</reg>
</choice>
</l> |
6.1.134. <p>
| <p> (paragraph) marks paragraphs in prose. [3.1. Paragraphs 7.2.5. Speech Contents] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.fragmentable (@part) |
| Member of | |
| Contained by | drama: castList header: abstract application availability cRefPattern calendar change correction correspAction correspContext correspDesc editionStmt editorialDecl encodingDesc handNote hyphenation interpretation licence normalization prefixDef projectDesc publicationStmt punctuation quotation refsDecl samplingDecl scriptNote segmentation seriesStmt sourceDesc stdVals styleDefDecl typeNote namesdates: person transcr: metamark |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element p
{
att.global.attributes,
att.declaring.attributes,
att.fragmentable.attributes,
macro.paraContent
} |
| Schematron |
<s:report test="(ancestor::tei:p or ancestor::tei:ab) and not(parent::tei:exemplum
|parent::tei:item |parent::tei:note
|parent::tei:q |parent::tei:quote
|parent::tei:remarks |parent::tei:said
|parent::tei:sp |parent::tei:stage
|parent::tei:cell |parent::tei:figure)"> Abstract model violation: Paragraphs may not contain other paragraphs or ab elements.
</s:report> |
| Schematron |
<s:report test="ancestor::tei:l[not(.//tei:note//tei:p[. = current()])]"> Abstract model violation: Lines may not contain higher-level structural elements such as div, p, or ab.
</s:report> |
| Example | <p>Hallgerd was outside. <q>There is blood on your axe,</q> she said. <q>What have you
done?</q>
</p>
<p>
<q>I have now arranged that you can be married a second time,</q> replied Thjostolf.
</p>
<p>
<q>Then you must mean that Thorvald is dead,</q> she said.
</p>
<p>
<q>Yes,</q> said Thjostolf. <q>And now you must think up some plan for me.</q>
</p> |
6.1.135. <pb/>
| <pb/> (page break) marks the start of a new page in a paginated document. [3.10.3. Milestone Elements] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.edition (@ed, @edRef) att.spanning (@spanTo) att.breaking (@break) |
| Member of | |
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list listBibl measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc subst supplied surface surfaceGrp surplus zone verse: rhyme |
| May contain | Empty element |
| Declaration |
element pb
{
att.global.attributes,
att.typed.attributes,
att.edition.attributes,
att.spanning.attributes,
att.breaking.attributes,
empty
} |
| Schematron |
<s:report test="parent::*/text() and not (preceding-sibling::text() and
following-sibling::text())">please make sure pb elements are not at the start or end of mixed content </s:report> |
| Example | Page numbers may vary in different editions of a text. <p> ... <pb n="145" ed="ed2"/>
<!-- Page 145 in edition "ed2" starts here --> ... <pb n="283" ed="ed1"/>
<!-- Page 283 in edition "ed1" starts here--> ... </p> |
| Example | A page break may be associated with a facsimile image of the page it introduces by means of the facs attribute <body>
<pb n="1" facs="page1.png"/>
<!-- page1.png contains an image of the page;
the text it contains is encoded here -->
<p>
<!-- ... -->
</p>
<pb n="2" facs="page2.png"/>
<!-- similarly, for page 2 -->
<p>
<!-- ... -->
</p>
</body> |
| Note | A <pb/> element should appear at the start of the page which it identifies. The global n attribute indicates the number or other value associated with this page. This will normally be the page number or signature printed on it, since the physical sequence number is implicit in the presence of the <pb/> element itself.The type attribute may be used to characterize the page break in any respect, for example as word-breaking or not. |
6.1.136. <pc>
| <pc> (punctuation character) contains a character or string of characters regarded as constituting a single punctuation mark. [17.1. Linguistic Segment Categories] | |||||||||||||||||||||
| Module | analysis | ||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.segLike (@function) (att.fragmentable (@part)) att.typed (@type, @subtype)
| ||||||||||||||||||||
| Member of | |||||||||||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||||||||||||
| May contain | |||||||||||||||||||||
| Declaration |
element pc
{
att.global.attributes,
att.segLike.attributes,
att.typed.attributes,
attribute force { text }?,
attribute unit { data.enumerated }?,
attribute pre { data.truthValue }?,
( text | model.gLike | c | model.pPart.edit )*
} | ||||||||||||||||||||
| Example | <phr>
<w>do</w>
<w>you</w>
<w>understand</w>
<pc type="interrogative">?</pc>
</phr> | ||||||||||||||||||||
6.1.137. <person>
| <person> provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source. [13.3.2. The Person Element 15.2.2. The Participant Description] | |||||||||||||||||||||||||
| Module | namesdates | ||||||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.sortable (@sortKey)
| ||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||
| Contained by | namesdates: listPerson | ||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||
| Declaration |
element person
{
att.global.attributes,
att.editLike.attributes,
att.sortable.attributes,
attribute role { list { data.enumerated+ } }?,
attribute sex { list { data.sex+ } }?,
attribute age { data.enumerated }?,
( model.pLike+ | ( model.personPart | model.global )* )
} | ||||||||||||||||||||||||
| Example | <person sex="F" age="adult">
<p>Female respondent, well-educated, born in Shropshire UK, 12 Jan 1950, of unknown occupation. Speaks French fluently. Socio-Economic
status B2.</p>
</person> | ||||||||||||||||||||||||
| Example | <person sex="intersex" role="god"
age="immortal">
<persName>Hermaphroditos</persName>
<persName xml:lang="grc">Ἑρμαφρόδιτος</persName>
</person> | ||||||||||||||||||||||||
| Example | <person xml:id="Ovi01" sex="1" role="poet">
<persName xml:lang="en">Ovid</persName>
<persName xml:lang="la">Publius Ovidius Naso</persName>
<birth when="-0044-03-20"> 20 March 43 BC <placeName>
<settlement type="city">Sulmona</settlement>
<country key="IT">Italy</country>
</placeName>
</birth>
<death notBefore="0017" notAfter="0018">17 or 18 AD <placeName>
<settlement type="city">Tomis (Constanta)</settlement>
<country key="RO">Romania</country>
</placeName>
</death>
</person> | ||||||||||||||||||||||||
| Note | May contain either a prose description organized as paragraphs, or a sequence of more specific demographic elements drawn from the model.personPart class. | ||||||||||||||||||||||||
6.1.138. <physDesc>
| <physDesc> (physical description) contains a full physical description of a manuscript or manuscript part, optionally subdivided using more specialized elements from the model.physDescPart class. [10.7. Physical Description] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | msdescription: msDesc |
| May contain | |
| Declaration |
element physDesc
{
att.global.attributes,
( model.pLike*, ( model.physDescPart_sequenceOptional ) )
} |
| Example | <physDesc>
<objectDesc form="codex">
<supportDesc material="perg">
<support>Parchment.</support>
<extent>i + 55 leaves
<dimensions scope="all" type="leaf"
unit="inch">
<height>7¼</height>
<width>5⅜</width>
</dimensions>
</extent>
</supportDesc>
<layoutDesc>
<layout columns="2">In double columns.</layout>
</layoutDesc>
</objectDesc>
<handDesc>
<p>Written in more than one hand.</p>
</handDesc>
<decoDesc>
<p>With a few coloured capitals.</p>
</decoDesc>
</physDesc> |
6.1.139. <postscript>
| <postscript> contains a postscript, e.g. to a letter. [4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element postscript
{
att.global.attributes,
(
( model.global | model.divTopPart )*,
( model.common ),
( model.global | model.common )*,
( ( model.divBottomPart ), model.global* )*
)
} |
| Example | <div type="letter">
<opener>
<dateline>
<placeName>Rimaone</placeName>
<date when="2006-11-21">21 Nov 06</date>
</dateline>
<salute>Dear Susan,</salute>
</opener>
<p>Thank you very much for the assistance splitting those
logs. I'm sorry about the misunderstanding as to the size of
the task. I really was not asking for help, only to borrow the
axe. Hope you had fun in any case.</p>
<closer>
<salute>Sincerely yours,</salute>
<signed>Seymour</signed>
</closer>
<postscript>
<label>P.S.</label>
<p>The collision occured on <date when="2001-07-06">06 Jul 01</date>.</p>
</postscript>
</div> |
6.1.140. <prefixDef>
| <prefixDef> (prefixing scheme used in data.pointer values) defines a prefixing scheme used in data.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs. [16.2.3. Using Abbreviated Pointers] | |||||||
| Module | header | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.patternReplacement (@matchPattern, @replacementPattern)
| ||||||
| Contained by | header: listPrefixDef | ||||||
| May contain | |||||||
| Declaration |
element prefixDef
{
att.global.attributes,
att.patternReplacement.attributes,
attribute ident { data.name },
model.pLike*
} | ||||||
| Example | <prefixDef ident="ref"
matchPattern="([a-z]+)"
replacementPattern="../../references/references.xml#$1">
<p> In the context of this project, private URIs with
the prefix "ref" point to <gi>div</gi> elements in
the project's global references.xml file.
</p>
</prefixDef> | ||||||
| Note | The abbreviated pointer may be dereferenced to produce either an absolute or a relative URI reference. In the latter case it is combined with the value of xml:base in force at the place where the pointing attribute occurs to form an absolute URI in the usual manner as prescribed by XML Base. | ||||||
6.1.141. <principal>
| <principal> (principal researcher) supplies the name of the principal researcher responsible for the creation of an electronic text. [2.2.1. The Title Statement] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) |
| Member of | |
| Contained by | core: bibl header: editionStmt titleStmt |
| May contain | |
| Declaration |
element principal
{
att.global.attributes,
att.canonical.attributes,
macro.phraseSeq.limited
} |
| Example | <principal ref="http://viaf.org/viaf/105517912">Gary Taylor</principal> |
6.1.142. <profileDesc>
| <profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4. The Profile Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: teiHeader |
| May contain | corpus: textDesc transcr: listTranspose |
| Declaration |
element profileDesc { att.global.attributes, ( model.profileDescPart* ) } |
| Example | <profileDesc>
<langUsage>
<language ident="fr">French</language>
</langUsage>
<textDesc n="novel">
<channel mode="w">print; part issues</channel>
<constitution type="single"/>
<derivation type="original"/>
<domain type="art"/>
<factuality type="fiction"/>
<interaction type="none"/>
<preparedness type="prepared"/>
<purpose type="entertain" degree="high"/>
<purpose type="inform" degree="medium"/>
</textDesc>
<settingDesc>
<setting>
<name>Paris, France</name>
<time>Late 19th century</time>
</setting>
</settingDesc>
</profileDesc> |
| Note | Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of <profileDesc> unless these are documenting multiple texts.In earlier versions of these Guidelines, it was required that the <creation> element appear first. |
6.1.143. <projectDesc>
| <projectDesc> (project description) describes in detail the aim or purpose for which an electronic file was encoded, together with any other relevant information concerning the process by which it was assembled or collected. [2.3.1. The Project Description 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| Declaration |
element projectDesc { att.global.attributes, model.pLike+ } |
| Example | <projectDesc>
<p>Texts collected for use in the Claremont Shakespeare Clinic, June 1990</p>
</projectDesc> |
6.1.144. <pubPlace>
| <pubPlace> (publication place) contains the name of the place where a bibliographic item was published. [3.11.2.4. Imprint, Size of a Document, and Reprint Information] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element pubPlace
{
att.global.attributes,
att.naming.attributes,
macro.phraseSeq
} |
| Example | <publicationStmt>
<publisher>Oxford University Press</publisher>
<pubPlace>Oxford</pubPlace>
<date>1989</date>
</publicationStmt> |
6.1.145. <publicationStmt>
| <publicationStmt> (publication statement) groups information concerning the publication or distribution of an electronic or other text. [2.2.4. Publication, Distribution, Licensing, etc. 2.2. The File Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | |
| Declaration |
element publicationStmt
{
att.global.attributes,
(
(
( model.publicationStmtPart.agency ),
model.publicationStmtPart.detail*
)+
| model.pLike+
)
} |
| Example | <publicationStmt>
<publisher>C. Muquardt </publisher>
<pubPlace>Bruxelles & Leipzig</pubPlace>
<date when="1846"/>
</publicationStmt> |
| Example | <publicationStmt>
<publisher>Chadwyck Healey</publisher>
<pubPlace>Cambridge</pubPlace>
<availability>
<p>Available under licence only</p>
</availability>
<date when="1992">1992</date>
</publicationStmt> |
| Note | Where a publication statement contains several members of the model.publicationStmtPart classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order. |
6.1.146. <publisher>
| <publisher> provides the name of the organization responsible for the publication or distribution of a bibliographic item. [3.11.2.4. Imprint, Size of a Document, and Reprint Information 2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element publisher { att.global.attributes, macro.phraseSeq } |
| Example | <imprint>
<pubPlace>Oxford</pubPlace>
<publisher>Clarendon Press</publisher>
<date>1987</date>
</imprint> |
| Note | Use the full form of the name by which a company is usually referred to, rather than any abbreviation of it which may appear on a title page |
6.1.147. <punctuation>
| <punctuation> specifies editorial practice adopted with respect to punctuation marks in the original. [2.3.3. The Editorial Practices Declaration 3.2. Treatment of Punctuation] | |||||||||||||||||
| Module | header | ||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | header: editorialDecl | ||||||||||||||||
| May contain | |||||||||||||||||
| Declaration |
element punctuation
{
att.global.attributes,
attribute marks { text }?,
attribute placement { text }?,
model.pLike*
} | ||||||||||||||||
| Example | <punctuation marks="all"
placement="internal">
<p>All punctuation marks in the source text have been retained and represented using the
appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey
the same information (for example, a sentence ends with a question mark and is also tagged
as <gi>s</gi>) the punctuation mark is captured as content within the element.
</p>
</punctuation> | ||||||||||||||||
6.1.148. <q>
| <q> (quoted) contains material which is distinguished from the surrounding text using quotation marks or a similar method, for any one of a variety of reasons including, but not limited to: direct speech or thought, technical terms or jargon, authorial distance, quotations from elsewhere, and passages that are mentioned but not used. [3.3.3. Quotation] | |||||||||
| Module | core | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.ascribed (@who) att.source (@source)
| ||||||||
| Member of | |||||||||
| Contained by | drama: castList textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme | ||||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||
| Declaration |
element q
{
att.global.attributes,
att.ascribed.attributes,
att.source.attributes,
attribute type
{
"spoken"
| "thought"
| "written"
| "soCalled"
| "foreign"
| "distinct"
| "term"
| "emph"
| "mentioned"
| xsd:Name
}?,
macro.specialPara
} | ||||||||
| Example | It is spelled <q>Tübingen</q> — to enter the
letter <q>u</q> with an umlaut hold down the <q>option</q> key and press
<q>0 0 f c</q> | ||||||||
| Note | May be used to indicate that a passage is distinguished from the surrounding text for reasons concerning which no claim is made. When used in this manner, <q> may be thought of as syntactic sugar for <hi> with a value of rend that indicates the use of such mechanisms as quotation marks. | ||||||||
6.1.149. <quotation>
| <quotation> specifies editorial practice adopted with respect to quotation marks in the original. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements] | |||||||||
| Module | header | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | header: editorialDecl | ||||||||
| May contain | |||||||||
| Declaration |
element quotation
{
att.global.attributes,
attribute marks { text }?,
model.pLike*
} | ||||||||
| Schematron |
<s:report test="not(@marks) and not (tei:p)">On <s:name/>, either the @marks attribute should be used, or a paragraph of description provided</s:report> | ||||||||
| Example | <quotation marks="none">
<p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the
<gi>q</gi> element is used to specify what kinds of quotation mark was used, according
to the following list: <list type="gloss">
<label>dq</label>
<item>double quotes, open and close</item>
<label>sq</label>
<item>single quotes, open and close</item>
<label>dash</label>
<item>long dash open, no close</item>
<label>dg</label>
<item>double guillemets, open and close</item>
</list>
</p>
</quotation> | ||||||||
| Example | <quotation marks="all">
<p>All quotation marks are retained in the text and are represented by appropriate Unicode
characters.</p>
</quotation> | ||||||||
6.1.150. <quote>
| <quote> (quotation) contains a phrase or passage attributed by the narrator or author to some agency external to the text. [3.3.3. Quotation 4.3.1. Grouped Texts] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.source (@source) |
| Member of | |
| Contained by | drama: castList textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element quote
{
att.global.attributes,
att.typed.attributes,
att.source.attributes,
macro.specialPara
} |
| Example | Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized in his
slogan, <quote>You shall know a word by the company it
keeps</quote>
<ref>(Firth, 1957)</ref> |
| Note | If a bibliographic citation is supplied for the source of a quotation, the two may be grouped using the <cit> element. |
6.1.151. <redo/>
| <redo/> indicates one or more cancelled interventions in a document which have subsequently been marked as reaffirmed or repeated. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications] | |||||||
| Module | transcr | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.spanning (@spanTo) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) )
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||
| May contain | Empty element | ||||||
| Declaration |
element redo
{
att.global.attributes,
att.spanning.attributes,
att.transcriptional.attributes,
attribute target { list { data.pointer+ } }?,
empty
} | ||||||
| Example | <line>
<redo hand="#g_t" target="#redo-1"
cause="fix"/>
<mod xml:id="redo-1" rend="strikethrough"
spanTo="#anchor-1" hand="#g_bl"/>Ihr hagren, triſten, krummgezog<mod rend="strikethrough">nen</mod>ener Nacken
</line>
<line>Wenn ihr nur piepſet iſt die Welt ſchon matt.<anchor xml:id="anchor-1"/>
</line> This encoding represents the following sequence of events:
| ||||||
6.1.152. <ref>
| <ref> (reference) defines a reference to another location, possibly modified by additional text or comment. [3.6. Simple Links and Cross-References 16.1. Links] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.pointing (@targetLang, @target, @evaluate) att.internetMedia (@mimeType) att.typed (@type, @subtype) att.declaring (@decls) att.cReferencing (@cRef) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope biblStruct cit corr date del desc editor email expan foreign head hi item l label measure monogr name note num orig p pubPlace publisher q quote ref reg relatedItem resp rs sic speaker stage term time title unclear header: application authority catDesc change classCode correspContext creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element ref
{
att.global.attributes,
att.pointing.attributes,
att.internetMedia.attributes,
att.typed.attributes,
att.declaring.attributes,
att.cReferencing.attributes,
macro.paraContent
} |
| Schematron |
<s:report test="@target and @cRef">Only one of the
attributes @target' and @cRef' may be supplied on <s:name/></s:report> |
| Example | See especially <ref target="http://www.natcorp.ox.ac.uk/Texts/A02.xml#s2">the second
sentence</ref> |
| Example | See also <ref target="#locution">s.v. <term>locution</term>
</ref>. |
| Note | The target and cRef attributes are mutually exclusive. |
6.1.153. <refState/>
| <refState/> (reference state) specifies one component of a canonical reference defined by the milestone method. [2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration] | |||||||||||||||
| Module | header | ||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.milestoneUnit (@unit) att.edition (@ed, @edRef)
| ||||||||||||||
| Contained by | header: refsDecl | ||||||||||||||
| May contain | Empty element | ||||||||||||||
| Declaration |
element refState
{
att.global.attributes,
att.milestoneUnit.attributes,
att.edition.attributes,
attribute length { data.count }?,
attribute delim { data.text }?,
empty
} | ||||||||||||||
| Example | <refState unit="book" delim=":"/>
<refState unit="line" length="4"/> | ||||||||||||||
6.1.154. <refsDecl>
| <refsDecl> (references declaration) specifies how canonical references are constructed for this text. [2.3.6.3. Milestone Method 2.3. The Encoding Description 2.3.6. The Reference System Declaration] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| Declaration |
element refsDecl
{
att.global.attributes,
( model.pLike+ | cRefPattern+ | refState+ )
} |
| Example | <refsDecl>
<cRefPattern matchPattern="([A-Za-z0-9]+) ([0-9]+):([0-9]+)"
replacementPattern="#xpath(//body/div[@n='$1']/div[$2]/div3[$3])"/>
</refsDecl> This example is a formal representation for the referencing scheme described informally in the following example. |
| Example | <refsDecl>
<p>References are made up by concatenating the value for the
<att>n</att> attribute on the highest level <gi>div</gi>
element, followed by a space, followed by the sequential
number of the next level <gi>div</gi> followed by a colon
followed by the sequential number of the next (and lowest)
level <gi>div</gi>.</p>
</refsDecl> |
6.1.155. <reg>
| <reg> (regularization) contains a reading which has been regularized or normalized in some sense. [3.4.2. Regularization and Normalization 12. Critical Apparatus] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element reg
{
att.global.attributes,
att.editLike.attributes,
att.typed.attributes,
macro.paraContent
} |
| Example | If all that is desired is to call attention to the fact that the copy text has been regularized, <reg> may be used alone: <q>Please <reg>knock</reg> if an <reg>answer</reg> is <reg>required</reg>
</q> |
| Example | It is also possible to identify the individual responsible for the regularization, and, using the <choice> and <orig> elements, to provide both the original and regularized readings: <q>Please <choice>
<reg resp="#LB">knock</reg>
<orig>cnk</orig>
</choice> if an <choice>
<reg>answer</reg>
<orig>nsr</orig>
</choice> is <choice>
<reg>required</reg>
<orig>reqd</orig>
</choice>
</q> |
6.1.157. <rendition>
| <rendition> supplies information about the rendition or appearance of one or more elements in the source text. [2.3.4. The Tagging Declaration] | |||||||||||||||||||||||
| Module | header | ||||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.styleDef (@scheme, @schemeVersion)
| ||||||||||||||||||||||
| Contained by | header: tagsDecl | ||||||||||||||||||||||
| May contain | |||||||||||||||||||||||
| Declaration |
element rendition
{
att.global.attributes,
att.styleDef.attributes,
attribute scope { data.enumerated }?,
attribute selector { data.text }?,
macro.limitedContent
} | ||||||||||||||||||||||
| Example | <tagsDecl>
<rendition xml:id="r-center" scheme="css">text-align: center;</rendition>
<rendition xml:id="r-small" scheme="css">font-size: small;</rendition>
<rendition xml:id="r-large" scheme="css">font-size: large;</rendition>
<rendition xml:id="initcaps"
scope="first-letter" scheme="css">font-size: xx-large</rendition>
</tagsDecl> | ||||||||||||||||||||||
| Note | The present release of these Guidelines does not specify the content of this element in any further detail. It may be used to hold a description of the default rendition to be associated with the specified element, expressed in running prose, or in some more formal language such as CSS. | ||||||||||||||||||||||
6.1.158. <repository>
| <repository> contains the name of a repository within which manuscripts are stored, possibly forming part of an institution. [10.4. The Manuscript Identifier] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) |
| Contained by | msdescription: msIdentifier |
| May contain | gaiji: g |
| Declaration |
element repository
{
att.global.attributes,
att.naming.attributes,
macro.xtext
} |
| Example | <msIdentifier>
<settlement>Oxford</settlement>
<institution>University of Oxford</institution>
<repository>Bodleian Library</repository>
<idno>MS. Bodley 406</idno>
</msIdentifier> |
6.1.159. <resp>
| <resp> (responsibility) contains a phrase describing the nature of a person's intellectual responsibility, or an organization's role in the production or distribution of a work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) |
| Contained by | core: respStmt |
| May contain | |
| Declaration |
element resp
{
att.global.attributes,
att.canonical.attributes,
att.datable.attributes,
macro.phraseSeq.limited
} |
| Example | <respStmt>
<resp ref="http://id.loc.gov/vocabulary/relators/com.html">compiler</resp>
<name>Edward Child</name>
</respStmt> |
| Note | The attributes key or ref, inherited from the class att.canonical may be used to indicate the kind of responsibility in a normalized form, by referring directly (using ref) or indirectly (using key) to a standardized list of responsibility types, such as that maintained by a naming authority, for example the list maintained at http://www.loc.gov/marc/relators/relacode.html for bibliographic usage. |
6.1.160. <respStmt>
| <respStmt> (statement of responsibility) supplies a statement of responsibility for the intellectual content of a text, edition, recording, or series, where the specialized elements for authors, editors, etc. do not suffice or do not apply. May also be used to encode information about individuals or organizations which have played a role in the production or distribution of a bibliographic work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.2. The Edition Statement 2.2.5. The Series Statement] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) |
| Member of | |
| Contained by | header: editionStmt seriesStmt titleStmt |
| May contain | |
| Declaration |
element respStmt
{
att.global.attributes,
att.canonical.attributes,
( ( resp+, model.nameLike.agent+ ) | ( model.nameLike.agent+, resp+ ) )
} |
| Example | <respStmt>
<resp>transcribed from original ms</resp>
<persName>Claus Huitfeldt</persName>
</respStmt> |
| Example | <respStmt>
<resp>converted to XML encoding</resp>
<name>Alan Morrison</name>
</respStmt> |
6.1.161. <restore>
| <restore> indicates restoration of text to an earlier state by cancellation of an editorial or authorial marking or instruction. [11.3.1.6. Cancellation of Deletions and Other Markings] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element restore
{
att.global.attributes,
att.transcriptional.attributes,
att.typed.attributes,
macro.paraContent
} |
| Example | For I hate this
<restore hand="#dhl"
type="marginalStetNote">
<del>my</del>
</restore> body |
| Note | On this element, the type attribute categorizes the way that the cancelled intervention has been indicated in some way, for example by means of a marginal note, over-inking, additional markup, etc. |
6.1.162. <retrace>
| <retrace> contains a sequence of writing which has been retraced, for example by over-inking, to clarify or fix it. [11.3.4.3. Fixation and Clarification] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.spanning (@spanTo) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element retrace
{
att.global.attributes,
att.spanning.attributes,
att.transcriptional.attributes,
macro.paraContent
} |
| Note | Multiple retraces are indicated by nesting one <retrace> within another. In principle, a retrace differs from a substitution in that second and subsequent rewrites do not materially alter the content of an element. Where minor changes have been made during the retracing action however these may be marked up using <del>, <add>, etc. with an appropriate value for the change attribute. |
6.1.163. <revisionDesc>
| <revisionDesc> (revision description) summarizes the revision history for a file. [2.6. The Revision Description 2.1.1. The TEI Header and Its Components] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.docStatus (@status) |
| Contained by | header: teiHeader |
| May contain | core: list header: change listChange |
| Declaration |
element revisionDesc
{
att.global.attributes,
att.docStatus.attributes,
( list | listChange | change+ )
} |
| Example | <revisionDesc status="embargoed">
<change when="1991-11-11" who="#LB"> deleted chapter 10 </change>
</revisionDesc> |
| Note | If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any <change> to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list. |
6.1.164. <rhyme>
| <rhyme> marks the rhyming part of a metrical line. [6.5. Rhyme] | |||
| Module | verse | ||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype)
| ||
| Member of | |||
| Contained by | core: abbr add addrLine author biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||
| Declaration |
element rhyme
{
att.global.attributes,
att.typed.attributes,
attribute label { data.word }?,
macro.paraContent
} | ||
| Example | <lg rhyme="abababcc">
<l>'Tis pity learned virgins ever <rhyme label="a">wed</rhyme>
</l>
<l>With persons of no sort of edu<rhyme label="b">cation</rhyme>,</l>
<l>Or gentlemen, who, though well born and <rhyme label="a">bred</rhyme>,</l>
<l>Grow tired of scientific conver<rhyme label="b">sation</rhyme>:</l>
<l>I don't choose to say much on this <rhyme label="a">head</rhyme>,</l>
<l>I'm a plain man, and in a single <rhyme label="b">station</rhyme>,</l>
<l>But — Oh! ye lords of ladies inte<rhyme label="c">llectual</rhyme>,</l>
<l>Inform us truly, have they not hen-<rhyme label="a">peck'd you all</rhyme>?</l>
</lg> | ||
6.1.165. <role>
| <role> contains the name of a dramatic role, as given in a cast list. [7.1.4. Cast Lists] | |
| Module | drama |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | drama: castItem |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element role { att.global.attributes, macro.phraseSeq } |
| Example | <role xml:id="jt">Joan Trash</role>
<roleDesc>A Ginger-bread-woman</roleDesc> |
| Note | It is important to assign a meaningful ID attribute to the <role> element, since this ID is referred to by who attributes on many other elements. |
6.1.166. <roleDesc>
| <roleDesc> (role description) describes a character's role in a drama. [7.1.4. Cast Lists] | |
| Module | drama |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element roleDesc { att.global.attributes, macro.phraseSeq } |
| Example | <roleDesc>gentlemen of leisure</roleDesc> |
6.1.167. <row>
| <row> contains one row of a table. [14.1.1. TEI Tables] | |||||||||||
| Module | figures | ||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.tableDecoration (role, @rows, @cols)
| ||||||||||
| Contained by | figures: table | ||||||||||
| May contain | figures: cell | ||||||||||
| Declaration |
element row
{
att.global.attributes,
att.tableDecoration.attribute.rows,
att.tableDecoration.attribute.cols,
attribute role { text }?,
cell+
} | ||||||||||
| Example | <row role="data">
<cell role="label">Classics</cell>
<cell>Idle listless and unimproving</cell>
</row> | ||||||||||
6.1.168. <rs>
| <rs> (referencing string) contains a general purpose name or referring string. [13.2.1. Personal Names 3.5.1. Referring Strings] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.naming (@role, @nymRef) (att.canonical (@key, @ref)) att.typed (@type, @subtype) att.source (@source) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine address author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode correspAction creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element rs
{
att.global.attributes,
att.naming.attributes,
att.typed.attributes,
att.source.attributes,
macro.phraseSeq
} |
| Example | <q>My dear <rs type="person">Mr. Bennet</rs>, </q> said <rs type="person">his lady</rs>
to him one day,
<q>have you heard that <rs type="place">Netherfield Park</rs> is let at
last?</q> |
6.1.169. <s>
| <s> (s-unit) contains a sentence-like division of a text. [17.1. Linguistic Segment Categories 8.4.1. Segmentation] | |
| Module | analysis |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.segLike (@function) (att.fragmentable (@part)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element s
{
att.global.attributes,
att.segLike.attributes,
att.typed.attributes,
(
text
| model.gLike
| model.global
| binaryObject
| formula
| graphic
| media
| code
| distinct
| emph
| foreign
| gloss
| ident
| mentioned
| soCalled
| term
| title
| hi
| caesura
| rhyme
| address
| affiliation
| email
| date
| time
| depth
| dim
| geo
| height
| measure
| measureGrp
| num
| width
| name
| orgName
| persName
| geogFeat
| offset
| addName
| forename
| genName
| nameLink
| roleName
| surname
| bloc
| country
| district
| geogName
| placeName
| region
| settlement
| climate
| location
| population
| state
| terrain
| trait
| idno
| lang
| rs
| abbr
| am
| choice
| ex
| expan
| subst
| add
| corr
| damage
| del
| handShift
| mod
| orig
| redo
| reg
| restore
| retrace
| secl
| sic
| supplied
| surplus
| unclear
| undo
| catchwords
| dimensions
| heraldry
| locus
| locusGrp
| material
| objectType
| origDate
| origPlace
| secFol
| signatures
| stamp
| watermark
| att
| gi
| tag
| val
| ptr
| ref
| oRef
| oVar
| pRef
| pVar
| c
| cl
| m
| pc
| phr
| seg
| w
| specDesc
| specList
)*
} |
| Schematron |
<s:report test="tei:s">You may not nest one s element within
another: use seg instead</s:report> |
| Example | <head>
<s>A short affair</s>
</head>
<s>When are you leaving?</s>
<s>Tomorrow.</s> |
| Note | The <s> element may be used to mark orthographic sentences, or any other segmentation of a text, provided that the segmentation is end-to-end, complete, and non-nesting. For segmentation which is partial or recursive, the <seg> should be used instead.The type attribute may be used to indicate the type of segmentation intended, according to any convenient typology. |
6.1.170. <salute>
| <salute> (salutation) contains a salutation or greeting prefixed to a foreword, dedicatory epistle, or other division of a text, or the salutation in the closing of a letter, preface, etc. [4.2.2. Openers and Closers] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element salute { att.global.attributes, macro.paraContent } |
| Example | <salute>To all courteous mindes, that will voutchsafe the readinge.</salute> |
6.1.171. <samplingDecl>
| <samplingDecl> (sampling declaration) contains a prose description of the rationale and methods used in sampling texts in the creation of a corpus or collection. [2.3.2. The Sampling Declaration 2.3. The Encoding Description 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| Declaration |
element samplingDecl { att.global.attributes, model.pLike+ } |
| Example | <samplingDecl>
<p>Samples of up to 2000 words taken at random from the beginning, middle, or end of each
text identified as relevant by respondents.</p>
</samplingDecl> |
| Note | This element records all information about systematic inclusion or omission of portions of the text, whether a reflection of sampling procedures in the pure sense or of systematic omission of material deemed either too difficult to transcribe or not of sufficient interest. |
6.1.172. <scriptNote>
| <scriptNote> describes a particular script distinguished within the description of a manuscript or similar resource. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope) |
| Contained by | — |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element scriptNote
{
att.global.attributes,
att.handFeatures.attributes,
macro.specialPara
} |
| Example | <scriptNote scope="sole"/> |
6.1.173. <seg>
| <seg> (arbitrary segment) represents any segmentation of text below the ‘chunk’ level. [16.3. Blocks, Segments, and Anchors 6.2. Components of the Verse Line 7.2.5. Speech Contents] | |
| Module | linking |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.segLike (@function) (att.fragmentable (@part)) att.typed (@type, @subtype) att.source (@source) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element seg
{
att.global.attributes,
att.segLike.attributes,
att.typed.attributes,
att.source.attributes,
macro.paraContent
} |
| Example | <seg>When are you leaving?</seg>
<seg>Tomorrow.</seg> |
| Example | <s>
<seg rend="caps" type="initial-cap">So father's only</seg> glory was the ballfield.
</s> |
| Example | <seg type="preamble">
<seg>Sigmund, <seg type="patronym">the son of Volsung</seg>, was a king in Frankish country.</seg>
<seg>Sinfiotli was the eldest of his sons ...</seg>
<seg>Borghild, Sigmund's wife, had a brother ... </seg>
</seg> |
| Note | The <seg> element may be used at the encoder's discretion to mark any segments of the text of interest for processing. One use of the element is to mark text features for which no appropriate markup is otherwise defined. Another use is to provide an identifier for some segment which is to be pointed at by some other element—i.e. to provide a target, or a part of a target, for a <ptr> or other similar element. |
6.1.174. <segmentation>
| <segmentation> describes the principles according to which the text has been segmented, for example into sentences, tone-units, graphemic strata, etc. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: editorialDecl |
| May contain | |
| Declaration |
element segmentation { att.global.attributes, model.pLike+ } |
| Example | <segmentation>
<p>
<gi>s</gi> elements mark orthographic sentences and are numbered sequentially within
their parent <gi>div</gi> element </p>
</segmentation> |
| Example | <p>
<gi>seg</gi> elements are used to mark functional constituents of various types within each
<gi>s</gi>; the typology used is defined by a <gi>taxonomy</gi> element in the corpus
header <gi>classDecl</gi>
</p> |
6.1.175. <seriesStmt>
| <seriesStmt> (series statement) groups information about the series, if any, to which a publication belongs. [2.2.5. The Series Statement 2.2. The File Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | |
| Declaration |
element seriesStmt
{
att.global.attributes,
( model.pLike+ | ( title+, ( editor | respStmt )*, ( idno | biblScope )* ) )
} |
| Example | <seriesStmt>
<title>Machine-Readable Texts for the Study of Indian Literature</title>
<respStmt>
<resp>ed. by</resp>
<name>Jan Gonda</name>
</respStmt>
<biblScope unit="volume">1.2</biblScope>
<idno type="ISSN">0 345 6789</idno>
</seriesStmt> |
6.1.176. <sic>
| <sic> (Latin for thus or so ) contains text reproduced although apparently incorrect or inaccurate. [3.4.1. Apparent Errors] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.source (@source) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element sic { att.global.attributes, att.source.attributes, macro.paraContent } |
| Example | for his nose was as sharp as
a pen, and <sic>a Table</sic> of green fields. |
| Example | If all that is desired is to call attention to the apparent problem in the copy text, <sic> may be used alone: I don't know, Juan. It's so far in the past now
— how <sic>we can</sic> prove or disprove anyone's theories? |
| Example | It is also possible, using the <choice> and <corr> elements, to provide a corrected reading: I don't know, Juan. It's so far in the past now
— how <choice>
<sic>we can</sic>
<corr>can we</corr>
</choice> prove or disprove anyone's theories? |
| Example | for his nose was as sharp as
a pen, and <choice>
<sic>a Table</sic>
<corr>a' babbld</corr>
</choice> of green fields. |
6.1.177. <signed>
| <signed> (signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text. [4.2.2. Openers and Closers] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element signed { att.global.attributes, macro.paraContent } |
| Example | <signed>Thine to command <name>Humph. Moseley</name>
</signed> |
| Example | <closer>
<signed>Sign'd and Seal'd,
<list>
<item>John Bull,</item>
<item>Nic. Frog.</item>
</list>
</signed>
</closer> |
6.1.178. <sourceDesc>
| <sourceDesc> (source description) describes the source from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as "born digital" for a text which has no previous existence. [2.2.7. The Source Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | core: bibl biblStruct list listBibl p figures: table header: biblFull linking: ab msdescription: msDesc namesdates: listPerson |
| Declaration |
element sourceDesc
{
att.global.attributes,
(
model.pLike+
| ( model.biblLike | model.sourceDescPart | model.listLike )+
)
} |
| Example | <sourceDesc>
<bibl>
<title level="a">The Interesting story of the Children in the Wood</title>. In
<author>Victor E Neuberg</author>, <title>The Penny Histories</title>.
<publisher>OUP</publisher>
<date>1968</date>. </bibl>
</sourceDesc> |
| Example | <sourceDesc>
<p>Born digital: no previous source exists.</p>
</sourceDesc> |
6.1.179. <sourceDoc>
| <sourceDoc> contains a transcription or other representation of a single source document potentially forming part of a dossier génétique or collection of sources. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element sourceDoc
{
att.global.attributes,
att.declaring.attributes,
( ( model.global | model.graphicLike | surface | surfaceGrp )+ )
} |
| Example | <sourceDoc>
<surfaceGrp n="leaf1">
<surface facs="page1.png">
<zone>All the writing on page 1</zone>
</surface>
<surface>
<graphic url="page2-highRes.png"/>
<graphic url="page2-lowRes.png"/>
<zone>
<line>A line of writing on page 2</line>
<line>Another line of writing on page 2</line>
</zone>
</surface>
</surfaceGrp>
</sourceDoc> |
| Note | This element may be used as an alternative to <facsimile> for TEI documents containing only page images, or for documents containing both images and transcriptions. Transcriptions may be provided within the <surface> elements making up a source document, in parallel with them as part of a <text> element, or in both places if the encoder wishes to distinguish these two modes of transcription. |
6.1.180. <sp>
| <sp> (speech) contains an individual speech in a performance text, or a passage presented as such in a prose or verse text. [3.12.2. Core Tags for Drama 3.12. Passages of Verse or Drama 7.2.2. Speeches and Speakers] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.ascribed (@who) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element sp
{
att.global.attributes,
att.ascribed.attributes,
(
model.global*,
( speaker, model.global* )?,
(
(
lg
| model.lLike
| model.pLike
| model.listLike
| model.stageLike
| model.qLike
),
model.global*
)+
)
} |
| Example | <sp>
<speaker>The reverend Doctor Opimian</speaker>
<p>I do not think I have named a single unpresentable fish.</p>
</sp>
<sp>
<speaker>Mr Gryll</speaker>
<p>Bream, Doctor: there is not much to be said for bream.</p>
</sp>
<sp>
<speaker>The Reverend Doctor Opimian</speaker>
<p>On the contrary, sir, I think there is much to be said for him. In the first place....</p>
<p>Fish, Miss Gryll — I could discourse to you on fish by the hour: but for the present I
will forbear...</p>
</sp> |
| Note | The who attribute on this element may be used either in addition to the <speaker> element or as an alternative. |
| Note | Lines or paragraphs, stage directions, and phrase-level elements.The who attribute on this element may be used either in addition to the <speaker> element or as an alternative. |
6.1.181. <spGrp>
| <spGrp> (speech group) contains a group of speeches or songs in a performance text presented in a source as constituting a single unit or ‘number’. [7.2.3. Grouped Speeches] | |
| Module | drama |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) att.ascribed (@who) |
| Member of | |
| Contained by | |
| May contain | |
| Declaration |
element spGrp
{
att.global.attributes,
att.typed.attributes,
att.ascribed.attributes,
( model.headLike*, ( model.global | sp | model.stageLike )+ )
} |
| Example | <sp>
<speaker>FRAULEIN SCHNEIDER:</speaker>
<p> Herr Schultz! Can I believe what I see? <stage>(HERR SCHULTZ nods
proudly)</stage> But this is — too much to accept. So rare — so costly —
so luxurious. </p>
</sp>
<stage>(She sings)</stage>
<spGrp n="4">
<sp>
<l>If you bought me diamonds, If you bought me pearls,</l>
<l>If you bought me roses like some other gents</l>
<l>Might bring to other girls,</l>
<l>It couldn't please me more</l>
<l>Than the gift I see -</l>
<stage>(She takes a large pineapple out of the bag)</stage>
<l>A pineapple for me!</l>
</sp>
<sp>
<speaker>SCHULTZ:</speaker>
<stage>(Singing) </stage>
<l>If, in your emotion, </l>
<l>You began to sway, </l>
<l>Went to get some air, </l>
<l>Or grabbed a chair </l>
<l>To keep from fainting dead away, </l>
<l>It couldn't please me more </l>
<l>Than to see you cling </l>
<l>To the pineapple I bring.</l>
</sp>
<sp>
<speaker>BOTH:</speaker>
<l>Ah, ah, ah, ah, ah, ah, ah, ah</l>
</sp>
<!-- ... -->
<stage>(They dance)</stage>
</spGrp>
<sp>
<speaker>FRAULEIN SCHNEIDER: </speaker>
<p>But you must not bring me
any more pineapples! Do you hear? It is not proper. It is a gift a
young man would present to his lady love. It makes me blush!
</p>
</sp> |
6.1.182. <space>
| <space> indicates the location of a significant space in the text. [11.5.1. Space] | |||||||||||||||||||
| Module | transcr | ||||||||||||||||||
| Attributes | Attributes att.typed (@type, @subtype) att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.source (@source) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) att.global.rendition (@rendition) att.global.linking (@corresp, @sameAs, @next, @prev) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (resp, @cert)
| ||||||||||||||||||
| Member of | |||||||||||||||||||
| Contained by | core: abbr add addrLine address author bibl biblScope cit corr date del editor email expan foreign head hi imprint item l label lg list measure name note num orig p pubPlace publisher q quote ref reg resp rs sic sp speaker stage term time title unclear header: authority change classCode distributor edition extent funder geoDecl handNote language licence principal scriptNote sponsor typeNote namesdates: person textstructure: argument back body byline closer dateline div docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer transcr: damage fw line metamark mod restore retrace sourceDoc supplied surface surfaceGrp surplus zone verse: rhyme | ||||||||||||||||||
| May contain | core: desc | ||||||||||||||||||
| Declaration |
element space
{
att.global.attribute.xmlid,
att.global.attribute.n,
att.global.attribute.xmllang,
att.global.attribute.xmlbase,
att.global.attribute.xmlspace,
att.global.rendition.attribute.rendition,
att.global.linking.attribute.corresp,
att.global.linking.attribute.sameAs,
att.global.linking.attribute.next,
att.global.linking.attribute.prev,
att.global.analytic.attribute.ana,
att.global.facs.attribute.facs,
att.global.change.attribute.change,
att.global.responsibility.attribute.cert,
att.typed.attributes,
att.dimensions.attributes,
att.source.attributes,
attribute resp { list { data.pointer+ } }?,
attribute dim { text }?,
model.descLike*
} | ||||||||||||||||||
| Example | By god if wommen had writen storyes
As <space quantity="7" unit="minims"/> han within her oratoryes | ||||||||||||||||||
| Example | στρατηλάτ<space quantity="1" unit="chars"/>ου | ||||||||||||||||||
| Note | This element should be used wherever it is desired to record an unusual space in the source text, e.g. space left for a word to be filled in later, for later rubrication, etc. It is not intended to be used to mark normal inter-word space or the like. | ||||||||||||||||||
6.1.183. <speaker>
| <speaker> contains a specialized form of heading or label, giving the name of one or more speakers in a dramatic text or fragment. [3.12.2. Core Tags for Drama] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | core: sp |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element speaker { att.global.attributes, macro.phraseSeq } |
| Example | <sp who="#ni #rsa">
<speaker>Nancy and Robert</speaker>
<stage type="delivery">(speaking simultaneously)</stage>
<p>The future? ...</p>
</sp>
<list type="speakers">
<item xml:id="ni"/>
<item xml:id="rsa"/>
</list> |
6.1.184. <sponsor>
| <sponsor> specifies the name of a sponsoring organization or institution. [2.2.1. The Title Statement] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) |
| Member of | |
| Contained by | header: editionStmt titleStmt |
| May contain | |
| Declaration |
element sponsor
{
att.global.attributes,
att.canonical.attributes,
macro.phraseSeq.limited
} |
| Example | <sponsor>Association for Computers and the Humanities</sponsor>
<sponsor>Association for Computational Linguistics</sponsor>
<sponsor ref="http://www.allc.org/">Association for Literary and Linguistic Computing</sponsor> |
| Note | Sponsors give their intellectual authority to a project; they are to be distinguished from funders, who provide the funding but do not necessarily take intellectual responsibility. |
6.1.185. <stage>
| <stage> (stage direction) contains any kind of stage direction within a dramatic text or fragment. [3.12.2. Core Tags for Drama 3.12. Passages of Verse or Drama 7.2.4. Stage Directions] | |||||||||
| Module | core | ||||||||
| Attributes | Attributes att.ascribed (@who) att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.placement (@place)
| ||||||||
| Member of | |||||||||
| Contained by | textstructure: argument body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme | ||||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||
| Declaration |
element stage
{
att.ascribed.attributes,
att.global.attributes,
att.placement.attributes,
attribute type
{
"setting"
| "entrance"
| "exit"
| "business"
| "novelistic"
| "delivery"
| "modifier"
| "location"
| "mixed"
| xsd:Name
}?,
macro.specialPara
} | ||||||||
| Example | <stage type="setting">A curtain being drawn.</stage>
<stage type="setting">Music</stage>
<stage type="entrance">Enter Husband as being thrown off his horse.</stage>
<stage type="exit">Exit pursued by a bear.</stage>
<stage type="business">He quickly takes the stone out.</stage>
<stage type="delivery">To Lussurioso.</stage>
<stage type="novelistic">Having had enough, and embarrassed for the family.</stage>
<stage type="modifier">Disguised as Ansaldo.</stage>
<stage type="location">At a window.</stage>
<stage rend="inline" type="delivery">Aside.</stage> | ||||||||
| Example | <l>Behold. <stage n="*" place="margin">Here the vp<lb/>per part of the <hi>Scene</hi> open'd; when
straight appear'd a Heauen, and all the <hi>Pure Artes</hi> sitting on
two semi<lb/>circular ben<lb/>ches, one a<lb/>boue another: who sate thus till the rest of the
<hi>Prologue</hi> was spoken, which being ended, they descended in
order within the <hi>Scene,</hi> whiles the Musicke plaid</stage> Our
Poet knowing our free hearts</l> | ||||||||
| Note | The who attribute may be used to indicate more precisely the person or persons participating in the action described by the stage direction. | ||||||||
6.1.186. <stdVals>
| <stdVals> (standard values) specifies the format used when standardized date or number values are supplied. [2.3.3. The Editorial Practices Declaration 15.3.2. Declarable Elements] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: editorialDecl |
| May contain | |
| Declaration |
element stdVals { att.global.attributes, model.pLike+ } |
| Example | <stdVals>
<p>All integer numbers are left-filled with zeroes to 8 digits.</p>
</stdVals> |
6.1.187. <styleDefDecl>
| <styleDefDecl> (style definition language declaration) specifies the name of the formal language in which style or renditional information is supplied elsewhere in the document. The specific version of the scheme may also be supplied. [2.3.5. The Default Style Definition Language Declaration] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.styleDef (@scheme, @schemeVersion) |
| Member of | |
| Contained by | header: encodingDesc |
| May contain | |
| Declaration |
element styleDefDecl
{
att.global.attributes,
att.styleDef.attributes,
model.pLike*
} |
| Example | <styleDefDecl scheme="css"
schemeVersion="2.1"/>
<!-- ... -->
<tagsDecl>
<rendition xml:id="boldface">font-weight: bold;</rendition>
<rendition xml:id="italicstyle">font-style: italic;</rendition>
</tagsDecl> |
6.1.188. <subst>
| <subst> (substitution) groups one or more deletions with one or more additions when the combination is to be regarded as a single intervention in the text. [11.3.1.5. Substitutions] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) ) |
| Member of | |
| Contained by | core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | |
| Declaration |
element subst
{
att.global.attributes,
att.transcriptional.attributes,
( add | del | model.milestoneLike )+
} |
| Schematron |
<s:assert test="child::tei:add and child::tei:del">
<s:name/> must have at least one child add and at least one child del</s:assert> |
| Example | ... are all included. <del hand="#RG">It is</del>
<subst>
<add>T</add>
<del>t</del>
</subst>he expressed
|
| Example | that he and his Sister Miſs D — <lb/>who always lived with him, wd. be <subst>
<del>very</del>
<lb/>
<add>principally</add>
</subst> remembered in her Will.
|
| Example | <ab>τ<subst>
<add place="above">ῶν</add>
<del>α</del>
</subst>
συνκυρόντ<subst>
<add place="above">ων</add>
<del>α</del>
</subst>
ἐργαστηρί<subst>
<add place="above">ων</add>
<del>α</del>
</subst>
</ab> |
| Example | <subst>
<del>
<gap reason="illegible" quantity="5"
unit="character"/>
</del>
<add>apple</add>
</subst> |
6.1.189. <supplied>
| <supplied> signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |||||||
| Module | transcr | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||
| Declaration |
element supplied
{
att.global.attributes,
att.editLike.attributes,
attribute reason { list { data.word+ } }?,
macro.paraContent
} | ||||||
| Example | I am dr Sr yr
<supplied reason="illegible"
source="#amanuensis_copy">very humble Servt</supplied>
Sydney Smith | ||||||
| Example | <supplied reason="omitted-in-original">Dedication</supplied> to the duke of Bejar | ||||||
| Note | The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. | ||||||
6.1.190. <surface>
| <surface> defines a written surface as a two-dimensional coordinate space, optionally grouping one or more graphic representations of that space, zones of interest within that space, and transcriptions of the writing within them. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||||||||
| Module | transcr | ||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.declaring (@decls) att.typed (@type, @subtype)
| ||||||||||||||
| Contained by | transcr: facsimile sourceDoc surface surfaceGrp zone | ||||||||||||||
| May contain | |||||||||||||||
| Declaration |
element surface
{
att.global.attributes,
att.coordinated.attributes,
att.declaring.attributes,
att.typed.attributes,
attribute attachment { data.enumerated }?,
attribute flipping { data.truthValue }?,
(
( model.global | model.labelLike | model.graphicLike )*,
( ( zone | line | surface | surfaceGrp ), model.global* )*
)
} | ||||||||||||||
| Example | <facsimile>
<surface ulx="0" uly="0" lrx="200" lry="300">
<graphic url="Bovelles-49r.png"/>
</surface>
</facsimile> | ||||||||||||||
| Note | The <surface> element represents any two-dimensional space on some physical surface forming part of the source material, such as a piece of paper, a face of a monument, a billboard, a scroll, a leaf etc.The coordinate space defined by this element may be thought of as a grid lrx - ulx units wide and uly - lry units high. The <surface> element may contain graphic representations or transcriptions of written zones, or both. The coordinate values used by every <zone> element contained by this element are to be understood with reference to the same grid. Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements. | ||||||||||||||
6.1.191. <surfaceGrp>
| <surfaceGrp> defines any kind of useful grouping of written surfaces, for example the recto and verso of a single leaf, which the encoder wishes to treat as a single unit. [11.1. Digital Facsimiles] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.typed (@type, @subtype) |
| Contained by | transcr: facsimile sourceDoc surface surfaceGrp |
| May contain | |
| Declaration |
element surfaceGrp
{
att.global.attributes,
att.declaring.attributes,
att.typed.attributes,
( model.global | surface | surfaceGrp )+
} |
| Example | <sourceDoc>
<surfaceGrp>
<surface ulx="0" uly="0" lrx="200"
lry="300">
<graphic url="Bovelles-49r.png"/>
</surface>
<surface ulx="0" uly="0" lrx="200"
lry="300">
<graphic url="Bovelles-49v.png"/>
</surface>
</surfaceGrp>
</sourceDoc> |
| Note | Where it is useful or meaningful to do so, any grouping of multiple <surface> elements may be indicated using the <surfaceGrp> elements. |
6.1.192. <surplus>
| <surplus> marks text present in the source which the editor believes to be superfluous or redundant. [11.3.3.1. Damage, Illegibility, and Supplied Text] | |||||||
| Module | transcr | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||
| Declaration |
element surplus
{
att.global.attributes,
att.editLike.attributes,
attribute reason { list { data.word+ } }?,
macro.paraContent
} | ||||||
| Example | I am dr Sr yrs
<surplus reason="repeated">yrs</surplus>
Sydney Smith | ||||||
6.1.193. <table>
| <table> contains text displayed in tabular form, in rows and columns. [14.1.1. TEI Tables] | |||||||||||||||||
| Module | figures | ||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | drama: castList textstructure: argument back body div docEdition epigraph imprimatur postscript salute signed titlePart trailer verse: rhyme | ||||||||||||||||
| May contain | |||||||||||||||||
| Declaration |
element table
{
att.global.attributes,
attribute rows { data.count }?,
attribute cols { data.count }?,
(
( model.headLike | model.global )*,
( ( row, model.global* )+ | ( ( model.graphicLike ), model.global* )+ ),
( ( model.divBottom ), model.global* )*
)
} | ||||||||||||||||
| Example | <table rows="4" cols="4">
<head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)</head>
<row role="label">
<cell role="data"/>
<cell role="data">Dossing Cribs or Lodging Houses</cell>
<cell role="data">Beds</cell>
<cell role="data">Needys or Nightly Lodgers</cell>
</row>
<row role="data">
<cell role="label">Bury St Edmund's</cell>
<cell role="data">5</cell>
<cell role="data">8</cell>
<cell role="data">128</cell>
</row>
<row role="data">
<cell role="label">Thetford</cell>
<cell role="data">3</cell>
<cell role="data">6</cell>
<cell role="data">36</cell>
</row>
<row role="data">
<cell role="label">Attleboro'</cell>
<cell role="data">3</cell>
<cell role="data">5</cell>
<cell role="data">20</cell>
</row>
<row role="data">
<cell role="label">Wymondham</cell>
<cell role="data">1</cell>
<cell role="data">11</cell>
<cell role="data">22</cell>
</row>
</table> | ||||||||||||||||
| Note | Contains an optional heading and a series of rows.Any rendition information should be supplied using the global rend attribute, at the table, row, or cell level as appropriate. | ||||||||||||||||
6.1.194. <tag>
| <tag> contains text of a complete start- or end-tag, possibly including attribute specifications, but excluding the opening and closing markup delimiter characters. [22. Documentation Elements] | |||||||||||||||||
| Module | tagdocs | ||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||||||||
| Member of | |||||||||||||||||
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||||||||
| May contain | Character data only | ||||||||||||||||
| Declaration |
element tag
{
att.global.attributes,
attribute type { text }?,
attribute scheme { data.enumerated }?,
text
} | ||||||||||||||||
| Example | Mark the start of each italicised phrase with a
<tag>hi rend="it"</tag> tag, and its end with a <tag type="end">hi</tag> tag.
<tag type="comment">Example updated on 2008-04-05</tag> | ||||||||||||||||
6.1.195. <tagUsage>
| <tagUsage> supplies information about the usage of a specific element within a text. [2.3.4. The Tagging Declaration] | |||||||||||||||||||||||||
| Module | header | ||||||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||||||||||||||||
| Contained by | header: namespace | ||||||||||||||||||||||||
| May contain | |||||||||||||||||||||||||
| Declaration |
element tagUsage
{
att.global.attributes,
attribute gi { data.name },
attribute occurs { data.count }?,
attribute withId { data.count }?,
attribute render { list { data.pointer+ } }?,
macro.limitedContent
} | ||||||||||||||||||||||||
| Example | <tagsDecl>
<rendition xml:id="it">Render using a slant or italic variant on the current font</rendition>
<!-- ... -->
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="hi" occurs="28" withId="2"
render="#it"> Used to mark English words
italicized in the copy text.</tagUsage>
<tagUsage gi="foreign" render="#it">Used to mark non-English words in the copy text.</tagUsage>
<!-- ... -->
</namespace>
</tagsDecl> | ||||||||||||||||||||||||
6.1.196. <tagsDecl>
| <tagsDecl> (tagging declaration) provides detailed information about the tagging applied to a document. [2.3.4. The Tagging Declaration 2.3. The Encoding Description] | |||||||||
| Module | header | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | header: encodingDesc | ||||||||
| May contain | |||||||||
| Declaration |
element tagsDecl
{
att.global.attributes,
attribute partial { data.truthValue }?,
( rendition*, namespace* )
} | ||||||||
| Example | <tagsDecl>
<rendition xml:id="rend-it">to be rendered in italic font</rendition>
<namespace name="http://www.tei-c.org/ns/1.0">
<tagUsage gi="hi" occurs="467"
render="#rend-it"/>
<tagUsage gi="title" occurs="45"
render="#rend-it"/>
</namespace>
<namespace name="http://docbook.org/ns/docbook">
<tagUsage gi="para" occurs="10"/>
</namespace>
</tagsDecl> | ||||||||
6.1.197. <taxonomy>
| <taxonomy> defines a typology either implicitly, by means of a bibliographic citation, or explicitly by a structured taxonomy. [2.3.7. The Classification Declaration] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | header: classDecl |
| May contain | |
| Declaration |
element taxonomy
{
att.global.attributes,
(
( model.glossLike | model.descLike )*
| category+
| ( ( model.biblLike ), category* )
)
} |
| Example | <taxonomy xml:id="tax.b">
<bibl>Brown Corpus</bibl>
<category xml:id="tax.b.a">
<catDesc>Press Reportage</catDesc>
<category xml:id="tax.b.a1">
<catDesc>Daily</catDesc>
</category>
<category xml:id="tax.b.a2">
<catDesc>Sunday</catDesc>
</category>
<category xml:id="tax.b.a3">
<catDesc>National</catDesc>
</category>
<category xml:id="tax.b.a4">
<catDesc>Provincial</catDesc>
</category>
<category xml:id="tax.b.a5">
<catDesc>Political</catDesc>
</category>
<category xml:id="tax.b.a6">
<catDesc>Sports</catDesc>
</category>
</category>
<category xml:id="tax.b.d">
<catDesc>Religion</catDesc>
<category xml:id="tax.b.d1">
<catDesc>Books</catDesc>
</category>
<category xml:id="tax.b.d2">
<catDesc>Periodicals and tracts</catDesc>
</category>
</category>
</taxonomy> |
| Example | <taxonomy>
<category xml:id="literature">
<catDesc>Literature</catDesc>
<category xml:id="poetry">
<catDesc>Poetry</catDesc>
<category xml:id="sonnet">
<catDesc>Sonnet</catDesc>
<category xml:id="shakesSonnet">
<catDesc>Shakespearean Sonnet</catDesc>
</category>
<category xml:id="petraSonnet">
<catDesc>Petrarchan Sonnet</catDesc>
</category>
</category>
<category xml:id="haiku">
<catDesc>Haiku</catDesc>
</category>
</category>
<category xml:id="drama">
<catDesc>Drama</catDesc>
</category>
</category>
<category xml:id="meter">
<catDesc>Metrical Categories</catDesc>
<category xml:id="feet">
<catDesc>Metrical Feet</catDesc>
<category xml:id="iambic">
<catDesc>Iambic</catDesc>
</category>
<category xml:id="trochaic">
<catDesc>trochaic</catDesc>
</category>
</category>
<category xml:id="feetNumber">
<catDesc>Number of feet</catDesc>
<category xml:id="pentameter">
<catDesc>>Pentameter</catDesc>
</category>
<category xml:id="tetrameter">
<catDesc>>Tetrameter</catDesc>
</category>
</category>
</category>
</taxonomy>
<!-- elsewhere in document -->
<lg ana="#shakesSonnet #iambic #pentameter">
<l>Shall I compare thee to a summer's day</l>
<!-- ... -->
</lg> |
6.1.198. <teiCorpus>
| <teiCorpus> contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more TEI elements, each containing a single text header and a text. [4. Default Text Structure 15.1. Varieties of Composite Text] | |||||||||
| Module | core | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Contained by | core: teiCorpus | ||||||||
| May contain | |||||||||
| Declaration |
element teiCorpus
{
att.global.attributes,
attribute version { data.version }?,
(
teiHeader,
( ( model.resourceLike+, ( TEI | teiCorpus )* ) | ( TEI | teiCorpus )+ )
)
} | ||||||||
| Example | <teiCorpus version="5.2" xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<!-- header for corpus -->
</teiHeader>
<TEI>
<teiHeader>
<!-- header for first text -->
</teiHeader>
<text>
<!-- content of first text -->
</text>
</TEI>
<TEI>
<teiHeader>
<!-- header for second text -->
</teiHeader>
<text>
<!-- content of second text -->
</text>
</TEI>
<!-- more TEI elements here -->
</teiCorpus> | ||||||||
| Note | Must contain one TEI header for the corpus, and a series of <TEI> elements, one for each text.This element is mandatory when applicable. | ||||||||
6.1.199. <teiHeader>
| <teiHeader> (TEI header) supplies the descriptive and declarative information making up an electronic title page for every TEI-conformant document. [2.1.1. The TEI Header and Its Components 15.1. Varieties of Composite Text] | |||||||||||
| Module | header | ||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||||
| Contained by | |||||||||||
| May contain | |||||||||||
| Declaration |
element teiHeader
{
att.global.attributes,
attribute type { data.enumerated }?,
( fileDesc, model.teiHeaderPart*, revisionDesc? )
} | ||||||||||
| Example | <teiHeader>
<fileDesc>
<titleStmt>
<title>Shakespeare: the first folio (1623) in electronic form</title>
<author>Shakespeare, William (1564–1616)</author>
<respStmt>
<resp>Originally prepared by</resp>
<name>Trevor Howard-Hill</name>
</respStmt>
<respStmt>
<resp>Revised and edited by</resp>
<name>Christine Avern-Carr</name>
</respStmt>
</titleStmt>
<publicationStmt>
<distributor>Oxford Text Archive</distributor>
<address>
<addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
</address>
<idno type="OTA">119</idno>
<availability>
<p>Freely available on a non-commercial basis.</p>
</availability>
<date when="1968">1968</date>
</publicationStmt>
<sourceDesc>
<bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)</bibl>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>Originally prepared for use in the production of a series of old-spelling
concordances in 1968, this text was extensively checked and revised for use during the
editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
</projectDesc>
<editorialDecl>
<correction>
<p>Turned letters are silently corrected.</p>
</correction>
<normalization>
<p>Original spelling and typography is retained, except that long s and ligatured
forms are not encoded.</p>
</normalization>
</editorialDecl>
<refsDecl xml:id="ASLREF">
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>A reference is created by assembling the following, in the reverse order as that
listed here: <list>
<item>the <att>n</att> value of the preceding <gi>lb</gi>
</item>
<item>a period</item>
<item>the <att>n</att> value of the ancestor <gi>div2</gi>
</item>
<item>a space</item>
<item>the <att>n</att> value of the parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
<revisionDesc>
<list>
<item>
<date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
<item>
<date when="1989-03-01">1 Mar 89</date> LB made new file</item>
</list>
</revisionDesc>
</teiHeader> | ||||||||||
| Note | One of the few elements unconditionally required in any TEI document. | ||||||||||
6.1.200. <term>
| <term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4. Terms, Glosses, Equivalents, and Descriptions] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote keywords language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element term
{
att.global.attributes,
att.declaring.attributes,
att.pointing.attributes,
att.typed.attributes,
att.canonical.attributes,
att.sortable.attributes,
att.cReferencing.attributes,
macro.phraseSeq
} |
| Example | A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the history
of NLP over the last 20 years has been occupied with the design of parsers. |
| Example | We may define <term xml:id="TDPV" rend="sc">discoursal point of view</term> as
<gloss target="#TDPV">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the
fiction.</gloss> |
| Note | This element is used to supply the form under which an index entry is to be made for the location of a parent <index> element.In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion. As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release. |
6.1.201. <text>
| <text> contains a single text of any kind, whether unitary or composite, for example a poem or drama, a collection of essays, a novel, a dictionary, or a corpus sample. [4. Default Text Structure 15.1. Varieties of Composite Text] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.declaring (@decls) att.typed (@type, @subtype) |
| Contained by | |
| May contain | |
| Declaration |
element text
{
att.global.attributes,
att.declaring.attributes,
att.typed.attributes,
(
model.global*,
( front, model.global* )?,
( body | group ),
model.global*,
( back, model.global* )?
)
} |
| Schematron |
<s:rule context="tei:att | tei:biblFull | tei:biblScope | tei:biblStruct | tei:change
| tei:charDecl | tei:charProp | tei:editor | tei:editorialDecl | tei:email
| tei:encodingDesc | tei:extent | tei:fileDesc | tei:gi | tei:glyph
| tei:glyphName | tei:idno | tei:imprint | tei:keywords | tei:licence
| tei:listChange | tei:listPerson | tei:localName | tei:monogr | tei:msDesc
| tei:msIdentifier | tei:person | tei:physDesc | tei:profileDesc |
tei:publicationStmt | tei:relatedItem | tei:repository | tei:resp
| tei:respStmt | tei:sourceDesc | tei:tag | tei:teiHeader | tei:term
| tei:textClass | tei:textDesc | tei:titleStmt | tei:typeDesc | tei:val
| tei:value">
<s:report test="ancestor::tei:text">Error: The element <s:name/> is not permitted outside the header</s:report></s:rule> |
| Example | <text>
<front>
<docTitle>
<titlePart>Autumn Haze</titlePart>
</docTitle>
</front>
<body>
<l>Is it a dragonfly or a maple leaf</l>
<l>That settles softly down upon the water?</l>
</body>
</text> |
| Example | The body of a text may be replaced by a group of nested texts, as in the following schematic: <text>
<front>
<!-- front matter for the whole group -->
</front>
<group>
<text>
<!-- first text -->
</text>
<text>
<!-- second text -->
</text>
</group>
</text> |
| Note | This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose. |
6.1.202. <textClass>
| <textClass> (text classification) groups information which describes the nature or topic of a text in terms of a standard classification scheme, thesaurus, etc. [2.4.3. The Text Classification] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: profileDesc |
| May contain | |
| Declaration |
element textClass { att.global.attributes, ( classCode | catRef | keywords )* } |
| Example | <taxonomy>
<category xml:id="acprose">
<catDesc>Academic prose</catDesc>
</category>
<!-- other categories here -->
</taxonomy>
<!-- ... -->
<textClass>
<catRef target="#acprose"/>
<classCode scheme="http://www.udcc.org">001.9</classCode>
<keywords scheme="http://authorities.loc.gov">
<list>
<item>End of the world</item>
<item>History - philosophy</item>
</list>
</keywords>
</textClass> |
6.1.203. <textDesc>
| <textDesc> (text description) provides a description of a text in terms of its situational parameters. [15.2.1. The Text Description] | |
| Module | corpus |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | header: catDesc profileDesc |
| May contain | Empty element |
| Declaration |
element textDesc
{
att.global.attributes,
( model.textDescPart_sequence, purpose+ )
} |
| Example | <textDesc n="Informal domestic conversation">
<channel mode="s"/>
<constitution type="single"/>
<derivation type="original"/>
<domain type="domestic"/>
<factuality type="mixed"/>
<interaction type="complete"
active="plural" passive="many"/>
<preparedness type="spontaneous"/>
<purpose type="entertain" degree="high"/>
<purpose type="inform" degree="medium"/>
</textDesc> |
6.1.204. <time>
| <time> contains a phrase defining a time of day in any format. [3.5.4. Dates and Times] | |
| Module | core |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.datable (@calendar, @period) (att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi imprint item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode correspAction creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | core: abbr add address cb choice corr date del email expan foreign gap graphic hi lb measure milestone name note num orig pb ref reg rs sic term time title unclear gaiji: g header: idno transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element time
{
att.global.attributes,
att.datable.attributes,
att.editLike.attributes,
att.typed.attributes,
( text | model.gLike | model.phrase | model.global )*
} |
| Example | As he sat smiling, the
quarter struck — <time when="11:45:00">the quarter to twelve</time>. |
6.1.205. <title>
| <title> contains a title for any kind of work. [3.11.2.2. Titles, Authors, and Editors 2.2.1. The Title Statement 2.2.5. The Series Statement] | |||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.canonical (@key, @ref) att.typed (type, @subtype)
| ||||||||||||||||||||||
| Member of | |||||||||||||||||||||||
| Contained by | analysis: s core: abbr add addrLine author bibl biblScope corr date del desc editor email expan foreign head hi item l label measure monogr name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote seriesStmt sponsor tagUsage titleStmt typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||||||||||||||||
| Declaration |
element title
{
att.global.attributes,
att.canonical.attributes,
att.typed.attribute.subtype,
attribute type { data.enumerated }?,
attribute level { text }?,
macro.paraContent
} | ||||||||||||||||||||||
| Example | <title>Information Technology and the Research Process: Proceedings of
a conference held at Cranfield Institute of Technology, UK,
18–21 July 1989</title> | ||||||||||||||||||||||
| Example | <title>Hardy's Tess of the D'Urbervilles: a machine readable
edition</title> | ||||||||||||||||||||||
| Example | <title type="full">
<title type="main">Synthèse</title>
<title type="sub">an international journal for
epistemology, methodology and history of
science</title>
</title> | ||||||||||||||||||||||
| Note | The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title. | ||||||||||||||||||||||
6.1.206. <titlePage>
| <titlePage> (title page) contains the title page of a text, appearing within the front or back matter. [4.6. Title Pages] | |||||||||
| Module | textstructure | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | figures: figure linking: anchor textstructure: argument byline docAuthor docDate docEdition docImprint docTitle epigraph imprimatur titlePart transcr: addSpan damageSpan fw listTranspose metamark space | ||||||||
| Declaration |
element titlePage
{
att.global.attributes,
attribute type { data.enumerated }?,
(
model.global*,
( model.titlepagePart ),
( model.titlepagePart | model.global )*
)
} | ||||||||
| Example | <titlePage>
<docTitle>
<titlePart type="main">THOMAS OF Reading.</titlePart>
<titlePart type="alt">OR, The sixe worthy yeomen of the West.</titlePart>
</docTitle>
<docEdition>Now the fourth time corrected and enlarged</docEdition>
<byline>By T.D.</byline>
<figure>
<head>TP</head>
<p>Thou shalt labor till thou returne to duste</p>
<figDesc>Printers Ornament used by TP</figDesc>
</figure>
<docImprint>Printed at <name type="place">London</name> for <name>T.P.</name>
<date>1612.</date>
</docImprint>
</titlePage> | ||||||||
6.1.207. <titlePart>
| <titlePart> contains a subsection or division of the title of a work, as indicated on a title page. [4.6. Title Pages] | |||||||||
| Module | textstructure | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp))
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||
| Declaration |
element titlePart
{
att.global.attributes,
attribute type { "main" | "sub" | "alt" | "short" | "desc" | xsd:Name }?,
macro.paraContent
} | ||||||||
| Example | <docTitle>
<titlePart type="main">THE FORTUNES
AND MISFORTUNES Of the FAMOUS
Moll Flanders, &c.
</titlePart>
<titlePart type="desc">Who was BORN in NEWGATE,
And during a Life of continu'd Variety for
Threescore Years, besides her Childhood, was
Twelve Year a <hi>Whore</hi>, five times a <hi>Wife</hi> (wherof
once to her own Brother) Twelve Year a <hi>Thief,</hi>
Eight Year a Transported <hi>Felon</hi> in <hi>Virginia</hi>,
at last grew <hi>Rich</hi>, liv'd <hi>Honest</hi>, and died a
<hi>Penitent</hi>.</titlePart>
</docTitle> | ||||||||
6.1.208. <titleStmt>
| <titleStmt> (title statement) groups information about the title of a work and those responsible for its content. [2.2.1. The Title Statement 2.2. The File Description] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | |
| May contain | |
| Declaration |
element titleStmt { att.global.attributes, ( title+, model.respLike* ) } |
| Example | <titleStmt>
<title>Capgrave's Life of St. John Norbert: a machine-readable transcription</title>
<respStmt>
<resp>compiled by</resp>
<name>P.J. Lucas</name>
</respStmt>
</titleStmt> |
6.1.209. <trailer>
| <trailer> contains a closing title or footer appearing at the end of a division of a text. [4.2.4. Content of Textual Divisions 4.2. Elements Common to All Divisions] | |
| Module | textstructure |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element trailer
{
att.global.attributes,
att.typed.attributes,
(
text
| lg
| model.gLike
| model.phrase
| model.inter
| model.lLike
| model.global
)*
} |
| Example | <trailer>Explicit pars tertia</trailer> |
| Example | <trailer>
<l>In stead of FINIS this advice <hi>I</hi> send,</l>
<l>Let Rogues and Thieves beware of <lb/>
<hi>Hamans</hi> END.</l>
</trailer> From EEBO A87070 |
6.1.210. <transpose>
| <transpose> describes a single textual transposition as an ordered list of at least two pointers specifying the order in which the elements indicated should be re-combined. [11.3.4.5. Transpositions] | |
| Module | transcr |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | transcr: listTranspose |
| May contain | Empty element |
| Declaration |
element transpose { att.global.attributes, ( ptr, ptr+ ) } |
| Example | <transpose>
<ptr target="#ib02"/>
<ptr target="#ib01"/>
</transpose> The transposition recorded here indicates that the content of the element with identifier ib02 should appear before the content of the element with identifier ib01. |
| Note | Transposition is usually indicated in a document by a metamark such as a wavy line or numbering. The order in which <ptr> elements appear within a <transpose> element should correspond with the desired order, as indicated by the metamark. |
6.1.211. <typeDesc>
| <typeDesc> contains a description of the typefaces or other aspects of the printing of an incunable or other printed source. [10.7.2.1. Writing] | |
| Module | msdescription |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | msdescription: physDesc |
| May contain | |
| Declaration |
element typeDesc
{
att.global.attributes,
( model.pLike+ | ( summary?, typeNote+ ) )
} |
| Example | <typeDesc>
<p>Uses an unidentified black letter font, probably from the
15th century</p>
</typeDesc> |
| Example | <typeDesc>
<summary>Contains a mixture of blackletter and Roman (antiqua) typefaces</summary>
<typeNote xml:id="Frak1">Blackletter face, showing
similarities to those produced in Wuerzburg after 1470.</typeNote>
<typeNote xml:id="Rom1">Roman face of Venetian origins.</typeNote>
</typeDesc> |
6.1.212. <typeNote>
| <typeNote> describes a particular font or other significant typographic feature distinguished within the description of a printed resource. [10.7.2. Writing, Decoration, and Other Notations] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.handFeatures (@scribe, @scribeRef, @script, @scriptRef, @medium, @scope) |
| Contained by | msdescription: typeDesc |
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig p pb q quote ref reg rs sic sp stage term time title unclear gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme |
| Declaration |
element typeNote
{
att.global.attributes,
att.handFeatures.attributes,
macro.specialPara
} |
| Example | <typeNote scope="sole"> Printed in an Antiqua typeface showing strong Italianate influence.
</typeNote> |
6.1.213. <unclear>
| <unclear> contains a word, phrase, or passage which cannot be transcribed with certainty because it is illegible or inaudible in the source. [11.3.3.1. Damage, Illegibility, and Supplied Text 3.4.3. Additions, Deletions, and Omissions] | |||||||||||||||||||||||||
| Module | core | ||||||||||||||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
| ||||||||||||||||||||||||
| Member of | |||||||||||||||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope choice corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||||||||||||||||
| May contain | core: abbr add address bibl biblStruct cb choice cit corr date del desc email expan foreign gap graphic hi l label lb lg list listBibl measure milestone name note num orig pb q quote ref reg rs sic stage term time title unclear drama: castList gaiji: g msdescription: msDesc namesdates: listPerson textstructure: floatingText transcr: addSpan am damage damageSpan ex fw handShift listTranspose metamark mod redo restore retrace space subst supplied surplus undo verse: rhyme | ||||||||||||||||||||||||
| Declaration |
element unclear
{
att.global.attributes,
att.editLike.attributes,
attribute reason { list { data.word+ } }?,
attribute hand { data.pointer }?,
attribute agent { data.enumerated }?,
macro.paraContent
} | ||||||||||||||||||||||||
| Example | <u> ...and then <unclear reason="background-noise">Nathalie</unclear> said ... </u> | ||||||||||||||||||||||||
| Note | The same element is used for all cases of uncertainty in the transcription of element content, whether for written or spoken material. For other aspects of certainty, uncertainty, and reliability of tagging and transcription, see chapter 21. Certainty, Precision, and Responsibility.The <damage>, <gap>, <del>, <unclear> and <supplied> elements may be closely allied in use. See section 11.3.3.2. Use of the gap, del, damage, unclear, and supplied Elements in Combination for discussion of which element is appropriate for which circumstance. The hand attribute points to a definition of the hand concerned, as further discussed in section 11.3.2.1. Document Hands. | ||||||||||||||||||||||||
6.1.214. <undo/>
| <undo/> indicates one or more marked-up interventions in a document which have subsequently been marked for cancellation. [11.3.4.4. Confirmation, Cancellation, and Reinstatement of Modifications] | |||||||
| Module | transcr | ||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.spanning (@spanTo) att.transcriptional (@hand, @status, @cause, @seq) (att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source)) )
| ||||||
| Member of | |||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||
| May contain | Empty element | ||||||
| Declaration |
element undo
{
att.global.attributes,
att.spanning.attributes,
att.transcriptional.attributes,
attribute target { list { data.pointer+ } }?,
empty
} | ||||||
| Example | <line>This is <del change="#s2" rend="overstrike">
<seg xml:id="undo-a">just some</seg>
sample <seg xml:id="undo-b">text</seg>,
we need</del>
<add change="#s2">not</add>
a real example.</line>
<undo target="#undo-a #undo-b"
rend="dotted" change="#s3"/> This encoding represents the following sequence of events:
| ||||||
6.1.215. <val>
| <val> (value) contains a single attribute value. [22. Documentation Elements 22.4.5. Attribute List Specification] | |
| Module | tagdocs |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Member of | |
| Contained by | analysis: s core: abbr add addrLine author biblScope corr date del desc editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg resp rs sic speaker stage term time title unclear header: authority catDesc change classCode creation distributor edition extent funder geoDecl handNote language licence principal rendition scriptNote sponsor tagUsage typeNote textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme |
| May contain | Character data only |
| Declaration |
element val { att.global.attributes, text } |
| Example | <val>unknown</val> |
6.1.216. <value>
| <value> contains a single value for some property, attribute, or other analysis. [5.2.1. Character Properties] | |
| Module | gaiji |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) |
| Contained by | gaiji: charProp |
| May contain | gaiji: g |
| Declaration |
element value { att.global.attributes, macro.xtext } |
| Example | <value>unknown</value> |
6.1.217. <w>
| <w> (word) represents a grammatical (not necessarily orthographic) word. [17.1. Linguistic Segment Categories] | |||||||||||||
| Module | analysis | ||||||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.segLike (@function) (att.fragmentable (@part)) att.typed (@type, @subtype)
| ||||||||||||
| Member of | |||||||||||||
| Contained by | core: abbr add addrLine author bibl biblScope corr date del editor email expan foreign head hi item l label measure name note num orig p pubPlace publisher q quote ref reg rs sic speaker stage term time title unclear figures: cell textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer verse: rhyme | ||||||||||||
| May contain | |||||||||||||
| Declaration |
element w
{
att.global.attributes,
att.segLike.attributes,
att.typed.attributes,
attribute lemma { data.text }?,
attribute lemmaRef { data.pointer }?,
(
text
| model.gLike
| seg
| w
| m
| c
| pc
| model.global
| model.lPart
| model.hiLike
| model.pPart.edit
)*
} | ||||||||||||
| Example | <w type="verb" lemma="hit"
lemmaRef="http://www.example.com/lexicon/hitvb.xml">hitt<m type="suffix">ing</m>
</w> | ||||||||||||
6.1.218. <xenoData>
| <xenoData> (outside metadata) provides a container element into which metadata in non-TEI formats may be placed. [2.5. Non-TEI Metadata] | |
| Module | header |
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.typed (@type, @subtype) |
| Member of | |
| Contained by | header: teiHeader |
| May contain | ANY |
| Declaration |
element xenoData
{
att.global.attributes,
att.typed.attributes,
text | macro.anyXML*
} |
| Example | This example presumes that the prefix dc has been bound to the namespace http://purl.org/dc/elements/1.1/ and the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#.<xenoData
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:RDF>
<rdf:Description rdf:about="http://www.worldcat.org/oclc/606621663">
<dc:title>The description of a new world, called the blazing-world</dc:title>
<dc:creator>The Duchess of Newcastle</dc:creator>
<dc:date>1667</dc:date>
<dc:identifier>British Library, 8407.h.10</dc:identifier>
<dc:subject>utopian fiction</dc:subject>
</rdf:Description>
</rdf:RDF>
</xenoData>
<xenoData>
<rdf:RDF>
<rdf:Description rdf:about="">
<dc:title>The Description of a New World, Called the Blazing-World, 1668</dc:title>
<dc:creator>Cavendish, Margaret (Lucas), Duchess of Newcastle</dc:creator>
<dc:publisher>Women Writers Project</dc:publisher>
<dc:date>2002-02-12</dc:date>
<dc:subject>utopian fiction</dc:subject>
</rdf:Description>
</rdf:RDF>
</xenoData> |
| Example | In this example, the prefix rdf is bound to the namespace http://www.w3.org/1999/02/22-rdf-syntax-ns#, the prefix dc is bound to the namespace http://purl.org/dc/elements/1.1/, and the prefix cc is bound to the namespace http://web.resource.org/cc/.<xenoData
xmlns:cc="http://web.resource.org/cc/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:RDF>
<cc:Work rdf:about="">
<dc:title>Applied Software Project Management - review</dc:title>
<dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
<dc:license rdf:resource="http://creativecommons.org/licenses/by-sa/2.0/uk/"/></cc:Work>
<cc:License rdf:about="http://creativecommons.org/licenses/by-sa/2.0/uk/">
<cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
<cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>
<cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>
<cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>
<cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
<cc:requires rdf:resource="http://web.resource.org/cc/ShareAlike"/></cc:License></rdf:RDF>
</xenoData> |
| Example | In this example, the prefix dc is again bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/, and the prefix oai_dc is bound to the namespace http://www.openarchives.org/OAI/2.0/oai_dc/.<xenoData
xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<oai_dc:dc>
<dc:title>The colonial despatches of Vancouver Island and British
Columbia 1846-1871: 11566, CO 60/2, p. 291; received 13 November.
Trevelyan to Merivale (Permanent Under-Secretary)</dc:title>
<dc:date>1858-11-12</dc:date>
<dc:creator>Trevelyan</dc:creator>
<dc:publisher>University of Victoria Humanities Computing and Media
Centre, and UVic Libraries</dc:publisher>
<dc:type>InteractiveResource</dc:type>
<dc:format>application/xhtml+xml</dc:format>
<dc:type>text</dc:type>
<dc:identifier>http://bcgenesis.uvic.ca/getDoc.htm?id=B585TE13.scx</dc:identifier>
<dc:rights>This document is licensed under a Creative Commons …</dc:rights>
<dc:language>(SCHEME=ISO639) en</dc:language>
<dc:source>Transcribed from microfilm and/or original documents, and
marked up in TEI P5 XML. The interactive XHTML resource is generated
from the XHTML using XQuery and XSLT.</dc:source>
<dc:source>repository: CO</dc:source>
<dc:source>coNumber: 60</dc:source>
<dc:source>coVol: 2</dc:source>
<dc:source>page: 291</dc:source>
<dc:source>coRegistration: 11566</dc:source>
<dc:source>received: received 13 November</dc:source>
<dc:subject>Trevelyan, Sir Charles Edward</dc:subject>
<dc:subject>Merivale, Herman</dc:subject>
<dc:subject>Elliot, T. Frederick</dc:subject>
<dc:subject>Moody, Colonel Richard Clement</dc:subject>
<dc:subject>Lytton, Sir Edward George Earle Bulwer</dc:subject>
<dc:subject>Jadis, Vane</dc:subject>
<dc:subject>Carnarvon, Earl</dc:subject>
<dc:subject>British Columbia</dc:subject>
<dc:description>British Columbia correspondence: Public Offices
document (normally correspondence between government
departments)</dc:description></oai_dc:dc>
</xenoData> |
| Example | In this example, the prefix mods is bound to the namespace http://www.loc.gov/mods/v3.<xenoData
xmlns:mods="http://www.loc.gov/mods/v3">
<mods:mods>
<mods:titleInfo>
<mods:title>Academic adaptation and cross-cultural
learning experiences of Chinese students at American
universities</mods:title>
<mods:subTitle>a narrative inquiry</mods:subTitle></mods:titleInfo>
<mods:name type="personal"
authority="local">
<mods:namePart/>
<mods:role>
<mods:roleTerm authority="marcrelator"
type="text">Author</mods:roleTerm></mods:role>
<mods:affiliation>Northeastern University</mods:affiliation>
<mods:namePart type="given">Hong</mods:namePart>
<mods:namePart type="family">Zhang</mods:namePart></mods:name>
<mods:name type="personal"
authority="local">
<mods:namePart/>
<mods:role>
<mods:roleTerm authority="local"
type="text">Advisor</mods:roleTerm></mods:role>
<mods:namePart type="given">Liliana</mods:namePart>
<mods:namePart type="family">Meneses</mods:namePart></mods:name>
<!-- ... -->
<mods:typeOfResource>text</mods:typeOfResource>
<mods:genre>doctoral theses</mods:genre>
<mods:originInfo>
<mods:place>
<mods:placeTerm type="text">Boston (Mass.)</mods:placeTerm></mods:place>
<mods:publisher>Northeastern University</mods:publisher>
<mods:copyrightDate encoding="w3cdtf"
keyDate="yes">2013</mods:copyrightDate></mods:originInfo>
<mods:language>
<mods:languageTerm authority="iso639-2b"
type="code">eng</mods:languageTerm></mods:language>
<mods:physicalDescription>
<mods:form authority="marcform">electronic</mods:form>
<mods:digitalOrigin>born digital</mods:digitalOrigin></mods:physicalDescription>
<!-- ... --></mods:mods>
</xenoData> |
6.1.219. <zone>
| <zone> defines any two-dimensional area within a <surface> element. [11.1. Digital Facsimiles 11.2.2. Embedded Transcription] | |||||||||
| Module | transcr | ||||||||
| Attributes | Attributes att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rendition)) (att.global.linking (@corresp, @sameAs, @next, @prev)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) att.coordinated (@start, @ulx, @uly, @lrx, @lry, @points) att.typed (@type, @subtype)
| ||||||||
| Member of | |||||||||
| Contained by | |||||||||
| May contain | |||||||||
| Declaration |
element zone
{
att.global.attributes,
att.coordinated.attributes,
att.typed.attributes,
attribute rotate { data.count }?,
( text | model.graphicLike | model.global | surface | model.linePart )*
} | ||||||||
| Example | <surface ulx="14.54" uly="16.14" lrx="0"
lry="0">
<graphic url="stone.jpg"/>
<zone points="4.6,6.3 5.25,5.85 6.2,6.6 8.19222,7.4125 9.89222,6.5875 10.9422,6.1375
11.4422,6.7125 8.21722,8.3125 6.2,7.65"/>
</surface> This example defines a non-rectangular zone: see the illustration in section [[undefined PH-surfzone]]. | ||||||||
| Example | <facsimile>
<surface ulx="50" uly="20" lrx="400"
lry="280">
<zone ulx="0" uly="0" lrx="500" lry="321">
<graphic url="graphic.png "/>
</zone>
</surface>
</facsimile> This example defines a zone which has been defined as larger than its parent surface in order to match the dimensions of the graphic it contains. | ||||||||
| Note | The position of every zone for a given surface is always defined by reference to the coordinate system defined for that surface. A graphic element contained by a zone represents the whole of the zone. A zone may be of any shape. The attribute points may be used to define a polygonal zone, using the coordinate system defined by its parent surface. | ||||||||
6.2. Model classes
6.2.1. model.addrPart
| model.addrPart groups elements such as names or postal codes which may appear as part of a postal address. [3.5.2. Addresses] | |
| Module | tei |
| Used by | |
| Members | model.nameLike[model.nameLike.agent[name] idno rs] addrLine |
6.2.2. model.addressLike
| model.addressLike groups elements used to represent a postal or email address. [1. The TEI Infrastructure] | |
| Module | tei |
| Used by | |
| Members | address email |
6.2.3. model.applicationLike
| model.applicationLike groups elements used to record application-specific information about a document in its header. | |
| Module | tei |
| Used by | |
| Members | application |
6.2.4. model.availabilityPart
| model.availabilityPart groups elements such as licences and paragraphs of text which may appear as part of an availability statement [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | licence |
6.2.5. model.biblLike
| model.biblLike groups elements containing a bibliographic description. [3.11. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | bibl biblFull biblStruct listBibl msDesc |
6.2.6. model.biblPart
| model.biblPart groups elements which represent components of a bibliographic description. [3.11. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | model.imprintPart[biblScope distributor pubPlace publisher] model.respLike[author editor funder principal respStmt sponsor] availability bibl edition extent msIdentifier relatedItem |
6.2.7. model.castItemPart
6.2.8. model.catDescPart
6.2.9. model.choicePart
6.2.10. model.common
| model.common groups common chunk- and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.divPart[model.lLike[l] model.pLike[ab p] lg sp spGrp] model.inter[model.biblLike[bibl biblFull biblStruct listBibl msDesc] model.labelLike[desc label] model.listLike[list listPerson table] model.qLike[model.quoteLike[cit quote] floatingText q] model.stageLike[stage] castList] |
| Note | This class defines the set of chunk- and inter-level elements; it is used in many content models, including those for textual divisions. |
6.2.11. model.correspActionPart
| model.correspActionPart groups elements which define the parts (usually names, dates and places) of one action related to the correspondence. | |
| Module | tei |
| Used by | |
| Members | model.addressLike[address email] model.dateLike[date time] model.nameLike[model.nameLike.agent[name] idno rs] note |
6.2.12. model.correspContextPart
| model.correspContextPart groups elements which may appear as part of the correspContext element | |
| Module | tei |
| Used by | |
| Members | model.pLike[ab p] model.ptrLike[ref] note |
6.2.13. model.correspDescPart
| model.correspDescPart groups together metadata elements for describing correspondence | |
| Module | tei |
| Used by | |
| Members | correspAction correspContext note |
6.2.14. model.dateLike
| model.dateLike groups elements containing temporal expressions. [3.5.4. Dates and Times 13.3.6. Dates and Times] | |
| Module | tei |
| Used by | |
| Members | date time |
6.2.15. model.descLike
6.2.16. model.divBottom
| model.divBottom groups elements appearing at the end of a text division. [4.2. Elements Common to All Divisions] | |
| Module | tei |
| Used by | |
| Members | model.divBottomPart[closer postscript signed trailer] model.divWrapper[argument byline dateline docAuthor docDate epigraph salute] |
6.2.17. model.divBottomPart
| model.divBottomPart groups elements which can occur only at the end of a text division. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | closer postscript signed trailer |
6.2.18. model.divLike
6.2.19. model.divPart
| model.divPart groups paragraph-level elements appearing directly within divisions. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.lLike[l] model.pLike[ab p] lg sp spGrp |
| Note | Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items. |
6.2.20. model.divTop
| model.divTop groups elements appearing at the beginning of a text division. [4.2. Elements Common to All Divisions] | |
| Module | tei |
| Used by | |
| Members | model.divTopPart[model.headLike[head] opener signed] model.divWrapper[argument byline dateline docAuthor docDate epigraph salute] |
6.2.21. model.divTopPart
| model.divTopPart groups elements which can occur only at the beginning of a text division. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | model.headLike[head] opener signed |
6.2.22. model.divWrapper
6.2.23. model.editorialDeclPart
| model.editorialDeclPart groups elements which may be used inside <editorialDecl> and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | correction hyphenation interpretation normalization punctuation quotation segmentation stdVals |
6.2.24. model.emphLike
| model.emphLike groups phrase-level elements which are typographically distinct and to which a specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | foreign term title |
6.2.25. model.encodingDescPart
| model.encodingDescPart groups elements which may be used inside <encodingDesc> and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | appInfo charDecl classDecl editorialDecl geoDecl listPrefixDef projectDesc refsDecl samplingDecl styleDefDecl tagsDecl |
6.2.26. model.frontPart
| model.frontPart groups elements which appear at the level of divisions within front or back matter. [7.1. Front and Back Matter ] | |
| Module | tei |
| Used by | |
| Members | model.frontPart.drama[castList] titlePage |
6.2.27. model.frontPart.drama
| model.frontPart.drama groups elements which appear at the level of divisions within front or back matter of performance texts only. [7.1. Front and Back Matter ] | |
| Module | tei |
| Used by | |
| Members | castList |
6.2.28. model.gLike
| model.gLike groups elements used to represent individual non-Unicode characters or glyphs. | |
| Module | tei |
| Used by | |
| Members | g |
6.2.29. model.global
| model.global groups elements which may appear at any point within a TEI text. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | address argument back bibl body byline castGroup castItem castList cit closer date dateline div docImprint docTitle epigraph figure floatingText front group head imprint l lg line list macro.paraContent macro.phraseSeq macro.phraseSeq.limited macro.specialPara opener person postscript s sourceDoc sp spGrp surface surfaceGrp table text time titlePage trailer w zone |
| Members | model.global.edit[addSpan damageSpan gap space] model.global.meta[listTranspose] model.milestoneLike[anchor cb fw lb milestone pb] model.noteLike[note] figure metamark |
6.2.30. model.global.edit
| model.global.edit groups globally available elements which perform a specifically editorial function. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | addSpan damageSpan gap space |
6.2.31. model.global.meta
| model.global.meta groups globally available elements which describe the status of other elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | listTranspose |
| Note | Elements in this class are typically used to hold groups of links or of abstract interpretations, or by provide indications of certainty etc. It may find be convenient to localize all metadata elements, for example to contain them within the same divison as the elements that they relate to; or to locate them all to a division of their own. They may however appear at any point in a TEI text. |
6.2.32. model.graphicLike
6.2.33. model.headLike
| model.headLike groups elements used to provide a title or heading at the start of a text division. | |
| Module | tei |
| Used by | |
| Members | head |
6.2.34. model.hiLike
| model.hiLike groups phrase-level elements which are typographically distinct but to which no specific function can be attributed. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | hi |
6.2.35. model.highlighted
| model.highlighted groups phrase-level elements which are typographically distinct. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | model.emphLike[foreign term title] model.hiLike[hi] |
6.2.36. model.imprintPart
| model.imprintPart groups the bibliographic elements which occur inside imprints. [3.11. Bibliographic Citations and References] | |
| Module | tei |
| Used by | |
| Members | biblScope distributor pubPlace publisher |
6.2.37. model.inter
| model.inter groups elements which can appear either within or between paragraph-like elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.biblLike[bibl biblFull biblStruct listBibl msDesc] model.labelLike[desc label] model.listLike[list listPerson table] model.qLike[model.quoteLike[cit quote] floatingText q] model.stageLike[stage] castList |
6.2.38. model.lLike
| model.lLike groups elements representing metrical components such as verse lines. | |
| Module | tei |
| Used by | |
| Members | l |
6.2.39. model.lPart
| model.lPart groups phrase-level elements which may appear within verse only. [6.2. Components of the Verse Line] | |
| Module | tei |
| Used by | |
| Members | rhyme |
6.2.40. model.labelLike
6.2.41. model.limitedPhrase
| model.limitedPhrase groups phrase-level elements excluding those elements primarily intended for transcription of existing sources. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.emphLike[foreign term title] model.hiLike[hi] model.pPart.data[model.addressLike[address email] model.dateLike[date time] model.measureLike[measure num] model.nameLike[model.nameLike.agent[name] idno rs]] model.pPart.editorial[abbr am choice ex expan subst] model.phrase.xml[att gi tag val] model.ptrLike[ref] |
6.2.42. model.linePart
| model.linePart groups transcriptional elements which appear within lines or zones of a source-oriented transcription within a <sourceDoc> element. | |
| Module | tei |
| Used by | |
| Members | model.hiLike[hi] model.pPart.transcriptional[add corr damage del handShift mod orig redo reg restore retrace sic supplied surplus unclear undo] model.segLike[c pc s seg w] choice line zone |
6.2.43. model.listLike
| model.listLike groups list-like elements. [3.7. Lists] | |
| Module | tei |
| Used by | |
| Members | list listPerson table |
6.2.44. model.measureLike
| model.measureLike groups elements which denote a number, a quantity, a measurement, or similar piece of text that conveys some numerical meaning. [3.5.3. Numbers and Measures] | |
| Module | tei |
| Used by | |
| Members | measure num |
6.2.45. model.milestoneLike
| model.milestoneLike groups milestone-style elements used to represent reference systems. [1.3. The TEI Class System 3.10.3. Milestone Elements] | |
| Module | tei |
| Used by | |
| Members | anchor cb fw lb milestone pb |
6.2.46. model.nameLike
| model.nameLike groups elements which name or refer to a person, place, or organization. | |
| Module | tei |
| Used by | |
| Members | model.nameLike.agent[name] idno rs |
| Note | A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc. |
6.2.47. model.nameLike.agent
| model.nameLike.agent groups elements which contain names of individuals or corporate bodies. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei |
| Used by | |
| Members | name |
| Note | This class is used in the content model of elements which reference names of people or organizations. |
6.2.48. model.noteLike
| model.noteLike groups globally-available note-like elements. [3.8. Notes, Annotation, and Indexing] | |
| Module | tei |
| Used by | |
| Members | note |
6.2.49. model.pLike
| model.pLike groups paragraph-like elements. | |
| Module | tei |
| Used by | abstract application availability back cRefPattern calendar correction correspAction correspDesc editionStmt editorialDecl encodingDesc front hyphenation interpretation model.correspContextPart model.divPart msDesc normalization person physDesc prefixDef projectDesc publicationStmt punctuation quotation refsDecl samplingDecl segmentation seriesStmt sourceDesc sp stdVals styleDefDecl typeDesc |
| Members | ab p |
6.2.50. model.pLike.front
| model.pLike.front groups paragraph-like elements which can occur as direct constituents of front matter. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | argument byline docAuthor docDate docEdition docImprint docTitle epigraph head titlePart |
6.2.51. model.pPart.data
| model.pPart.data groups phrase-level elements containing names, dates, numbers, measures, and similar data. [3.5. Names, Numbers, Dates, Abbreviations, and Addresses] | |
| Module | tei |
| Used by | |
| Members | model.addressLike[address email] model.dateLike[date time] model.measureLike[measure num] model.nameLike[model.nameLike.agent[name] idno rs] |
6.2.52. model.pPart.edit
| model.pPart.edit groups phrase-level elements for simple editorial correction and transcription. [3.4. Simple Editorial Changes] | |
| Module | tei |
| Used by | |
| Members | model.pPart.editorial[abbr am choice ex expan subst] model.pPart.transcriptional[add corr damage del handShift mod orig redo reg restore retrace sic supplied surplus unclear undo] |
6.2.53. model.pPart.editorial
6.2.54. model.pPart.transcriptional
6.2.55. model.personLike
| model.personLike groups elements which provide information about people and their relationships. | |
| Module | tei |
| Used by | |
| Members | person |
6.2.56. model.personPart
| model.personPart groups elements which form part of the description of a person. [15.2.2. The Participant Description] | |
| Module | tei |
| Used by | |
| Members | model.biblLike[bibl biblFull biblStruct listBibl msDesc] model.eventLike model.persStateLike idno |
6.2.57. model.phrase
| model.phrase groups elements which can occur at the level of individual words or phrases. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | model.graphicLike[formula graphic] model.highlighted[model.emphLike[foreign term title] model.hiLike[hi]] model.lPart[rhyme] model.pPart.data[model.addressLike[address email] model.dateLike[date time] model.measureLike[measure num] model.nameLike[model.nameLike.agent[name] idno rs]] model.pPart.edit[model.pPart.editorial[abbr am choice ex expan subst] model.pPart.transcriptional[add corr damage del handShift mod orig redo reg restore retrace sic supplied surplus unclear undo]] model.phrase.xml[att gi tag val] model.ptrLike[ref] model.segLike[c pc s seg w] |
| Note | This class of elements can occur within paragraphs, list items, lines of verse, etc. |
6.2.58. model.phrase.xml
| model.phrase.xml groups phrase-level elements used to encode XML constructs such as element names, attribute names, and attribute values [22. Documentation Elements] | |
| Module | tei |
| Used by | |
| Members | att gi tag val |
6.2.59. model.physDescPart
6.2.60. model.profileDescPart
| model.profileDescPart groups elements which may be used inside <profileDesc> and appear multiple times. | |
| Module | tei |
| Used by | |
| Members | abstract calendarDesc correspDesc creation langUsage listTranspose textClass textDesc |
6.2.61. model.ptrLike
| model.ptrLike groups elements used for purposes of location and reference. [3.6. Simple Links and Cross-References] | |
| Module | tei |
| Used by | |
| Members | ref |
6.2.62. model.publicationStmtPart.agency
| model.publicationStmtPart.agency groups the child elements of a <publicationStmt> element of the TEI header that indicate an authorising agent. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | authority distributor publisher |
| Note | The ‘agency’ child elements, while not required, are required if one of the ‘detail’ child elements is to be used. It is not valid to have a ‘detail’ child element without a preceding ‘agency’ child element.See also model.publicationStmtPart.detail. |
6.2.63. model.publicationStmtPart.detail
| model.publicationStmtPart.detail groups the agency-specific child elements of the <publicationStmt> element of the TEI header. [2.2.4. Publication, Distribution, Licensing, etc.] | |
| Module | tei |
| Used by | |
| Members | address availability date idno pubPlace |
| Note | A ‘detail’ child element may not occur unless an ‘agency’ child element precedes it.See also model.publicationStmtPart.agency. |
6.2.64. model.qLike
| model.qLike groups elements related to highlighting which can appear either within or between chunk-level elements. [3.3. Highlighting and Quotation] | |
| Module | tei |
| Used by | |
| Members | model.quoteLike[cit quote] floatingText q |
6.2.65. model.quoteLike
6.2.66. model.resourceLike
| model.resourceLike groups non-textual elements which may appear together with a header and a text to constitute a TEI document. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Members | facsimile sourceDoc |
6.2.67. model.respLike
6.2.68. model.segLike
| model.segLike groups elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |
| Module | tei |
| Used by | |
| Members | c pc s seg w |
| Note | The principles on which segmentation is carried out, and any special codes or attribute values used, should be defined explicitly in the <segmentation> element of the <encodingDesc> within the associated TEI header. |
6.2.69. model.stageLike
| model.stageLike groups elements containing stage directions or similar things defined by the module for performance texts. [7.3. Other Types of Performance Text] | |
| Module | tei |
| Used by | |
| Members | stage |
| Note | Stage directions are members of class inter: that is, they can appear between or within component-level elements. |
6.2.70. model.teiHeaderPart
| model.teiHeaderPart groups high level elements which may appear more than once in a TEI header. | |
| Module | tei |
| Used by | |
| Members | encodingDesc profileDesc xenoData |
6.2.71. model.titlepagePart
| model.titlepagePart groups elements which can occur as direct constituents of a title page, such as <docTitle>, <docAuthor>, <docImprint>, or <epigraph>. [4.6. Title Pages] | |
| Module | tei |
| Used by | |
| Members | argument byline docAuthor docDate docEdition docImprint docTitle epigraph graphic imprimatur titlePart |
6.3. Attribute classes
6.3.1. att.ascribed
| att.ascribed provides attributes for elements representing speech or action that can be ascribed to a specific individual. [3.3.3. Quotation 8.3. Elements Unique to Spoken Texts] | |||||||||||
| Module | tei | ||||||||||
| Members | change q sp spGrp stage | ||||||||||
| Attributes | Attributes
| ||||||||||
6.3.2. att.breaking
| att.breaking provides an attribute to indicate whether or not the element concerned is considered to mark the end of an orthographic token in the same way as whitespace. [3.10.3. Milestone Elements] | |||||||||||
| Module | tei | ||||||||||
| Members | cb lb milestone pb | ||||||||||
| Attributes | Attributes
| ||||||||||
6.3.3. att.cReferencing
| att.cReferencing provides an attribute which may be used to supply a canonical reference as a means of identifying the target of a pointer. | |||||||||
| Module | tei | ||||||||
| Members | ref term | ||||||||
| Attributes | Attributes
| ||||||||
6.3.4. att.canonical
| att.canonical provides attributes which can be used to associate a representation such as a name or title with canonical information about the object being named or referenced. | |||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||
| Members | att.naming[att.personal[name] author editor pubPlace repository rs] correspDesc docAuthor docTitle funder principal resp respStmt sponsor term title | ||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||
6.3.5. att.citing
| att.citing provides attributes for specifying the specific part of a bibliographic item being cited. [1.3.1. Attribute Classes] | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | biblScope | ||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||
6.3.6. att.coordinated
| att.coordinated elements which can be positioned within a two dimensional coordinate system. | |||||||||||||||||||||||||||||||||||||
| Module | transcr | ||||||||||||||||||||||||||||||||||||
| Members | line surface zone | ||||||||||||||||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||||||||||||||||
6.3.7. att.damaged
| att.damaged provides attributes describing the nature of any physical damage affecting a reading. [11.3.3.1. Damage, Illegibility, and Supplied Text 1.3.1. Attribute Classes] | |||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||
| Members | damage damageSpan | ||||||||||||||||||||||||||||
| Attributes | Attributes att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence))
| ||||||||||||||||||||||||||||
6.3.8. att.datable
| att.datable provides attributes for normalization of elements that contain dates, times, or datable events. [3.5.4. Dates and Times 13.3.6. Dates and Times] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | application change creation date licence name resp time | ||||||||||||||||||
| Attributes | Attributes att.datable.w3c (@when, @notBefore, @notAfter, @from, @to)
| ||||||||||||||||||
| Note | This ‘superclass’ provides attributes that can be used to provide normalized values of temporal information. By default, the attributes from the att.datable.w3c class are provided. If the module for names & dates is loaded, this class also provides attributes from the att.datable.iso and att.datable.custom classes. In general, the possible values of attributes restricted to the W3C datatypes form a subset of those values available via the ISO 8601 standard. However, the greater expressiveness of the ISO datatypes may not be needed, and there exists much greater software support for the W3C datatypes. | ||||||||||||||||||
6.3.9. att.datable.w3c
| att.datable.w3c provides attributes for normalization of elements that contain datable events conforming to the W3C XML Schema Part 2: Datatypes Second Edition. [3.5.4. Dates and Times 13.3.6. Dates and Times] | |||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||
| Members | att.datable[application change creation date licence name resp time] | ||||||||||||||||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||||||||||||||||
| Example | <date from="1863-05-28" to="1863-06-01">28 May through 1 June 1863</date> | ||||||||||||||||||||||||||||||||||||
| Note | The value of these attributes should be a normalized representation of the date, time, or combined date & time intended, in any of the standard formats specified by XML Schema Part 2: Datatypes Second Edition, using the Gregorian calendar.The most commonly-encountered format for the date portion of a temporal attribute is yyyy-mm-dd, but yyyy, --mm, ---dd, yyyy-mm, or --mm-dd may also be used. For the time part, the form hh:mm:ss is used.Note that this format does not currently permit use of the value 0000 to represent the year 1 BCE; instead the value -0001 should be used. | ||||||||||||||||||||||||||||||||||||
6.3.10. att.declaring
| att.declaring provides attributes for elements which may be independently associated with a particular declarable element within the header, thus overriding the inherited default for that element. [15.3. Associating Contextual Information with a Text] | |||||||
| Module | tei | ||||||
| Members | ab back body div facsimile floatingText front graphic group lg msDesc p ref sourceDoc surface surfaceGrp term text | ||||||
| Attributes | Attributes
| ||||||
| Note | The rules governing the association of declarable elements with individual parts of a TEI text are fully defined in chapter 15.3. Associating Contextual Information with a Text. | ||||||
6.3.11. att.dimensions
| att.dimensions provides attributes for describing the size of physical objects. | |||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||
| Members | att.damaged[damage damageSpan] att.editLike[att.transcriptional[add addSpan del mod redo restore retrace subst undo] am corr date ex expan gap name person reg supplied surplus time unclear] space | ||||||||||||||||||||||||||||||||||||||
| Attributes | Attributes att.ranging (@atLeast, @atMost, @min, @max, @confidence)
| ||||||||||||||||||||||||||||||||||||||
6.3.12. att.docStatus
| att.docStatus provides attributes for use on metadata elements describing the status of a document. | |||||||||
| Module | tei | ||||||||
| Members | bibl biblFull biblStruct change revisionDesc | ||||||||
| Attributes | Attributes
| ||||||||
| Example | <revisionDesc status="published">
<change when="2010-10-21"
status="published"/>
<change when="2010-10-02" status="cleared"/>
<change when="2010-08-02"
status="embargoed"/>
<change when="2010-05-01" status="frozen"
who="#MSM"/>
<change when="2010-03-01" status="draft"
who="#LB"/>
</revisionDesc> | ||||||||
6.3.13. att.editLike
| att.editLike provides attributes describing the nature of an encoded scholarly intervention or interpretation of any kind. [3.4. Simple Editorial Changes 10.3.1. Origination 13.3.2. The Person Element 11.3.1.1. Core Elements for Transcriptional Work] | |||||||||||||||||
| Module | tei | ||||||||||||||||
| Members | att.transcriptional[add addSpan del mod redo restore retrace subst undo] am corr date ex expan gap name person reg supplied surplus time unclear | ||||||||||||||||
| Attributes | Attributes att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) att.source (@source)
| ||||||||||||||||
| Note | The members of this attribute class are typically used to represent any kind of editorial intervention in a text, for example a correction or interpretation, or to date or localize manuscripts etc. | ||||||||||||||||
| Note | Each pointer on the source (if present) corresponding to a witness or witness group should reference a bibliographic citation such as a <witness>, <msDesc>, or <bibl> element, or another external bibliographic citation, documenting the source concerned. | ||||||||||||||||
6.3.14. att.edition
| att.edition provides attributes identifying the source edition from which some encoded feature derives. | |||||||||||||
| Module | tei | ||||||||||||
| Members | cb lb milestone pb refState | ||||||||||||
| Attributes | Attributes
| ||||||||||||
| Example | <l>Of Mans First Disobedience,<lb ed="1674"/> and<lb ed="1667"/> the Fruit</l>
<l>Of that Forbidden Tree, whose<lb ed="1667 1674"/> mortal tast</l>
<l>Brought Death into the World,<lb ed="1667"/> and all<lb ed="1674"/> our woe,</l> | ||||||||||||
| Example | <listBibl>
<bibl xml:id="stapledon1937">
<author>Olaf Stapledon</author>,
<title>Starmaker</title>, <publisher>Methuen</publisher>, <date>1937</date>
</bibl>
<bibl xml:id="stapledon1968">
<author>Olaf Stapledon</author>,
<title>Starmaker</title>, <publisher>Dover</publisher>, <date>1968</date>
</bibl>
</listBibl>
<!-- .... -->
<p>Looking into the future aeons from the supreme moment of
the cosmos, I saw the populations still with all their
strength maintaining the<pb n="411" edRef="#stapledon1968"/>essentials of their ancient culture,
still living their personal lives in zest and endless
novelty of action, … I saw myself still
preserving, though with increasing difficulty, my lucid
con-<pb n="291" edRef="#stapledon1937"/>sciousness;</p> | ||||||||||||
6.3.15. att.fragmentable
| att.fragmentable groups structural elements which may be fragmented, usually as a consequence of some overlapping hierarchy. | |||||||||||
| Module | tei | ||||||||||
| Members | att.segLike[c pc s seg w] ab l p | ||||||||||
| Attributes | Attributes
| ||||||||||
6.3.16. att.global
| att.global provides attributes common to all elements in the TEI encoding scheme. [1.3.1.1. Global Attributes] | |||||||||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||||||||
| Members | TEI ab abbr abstract actor add addSpan addrLine address am anchor appInfo application argument att author authority availability back bibl biblFull biblScope biblStruct body byline c cRefPattern calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change charDecl charProp choice cit classCode classDecl closer corr correction correspAction correspContext correspDesc creation damage damageSpan date dateline del desc distributor div docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email encodingDesc epigraph ex expan extent facsimile figDesc figure fileDesc floatingText foreign formula front funder fw g gap geoDecl gi glyph glyphName graphic group handNote handShift head hi hyphenation idno imprimatur imprint interpretation item keywords l label langUsage language lb lg licence line list listBibl listChange listPerson listPrefixDef listTranspose localName measure metamark milestone mod monogr msDesc msIdentifier name namespace normalization note notesStmt num opener orig p pb pc person physDesc postscript prefixDef principal profileDesc projectDesc pubPlace publicationStmt publisher punctuation q quotation quote redo ref refState refsDecl reg relatedItem rendition repository resp respStmt restore retrace revisionDesc rhyme role roleDesc row rs s salute samplingDecl scriptNote seg segmentation seriesStmt sic signed sourceDesc sourceDoc sp spGrp speaker sponsor stage stdVals styleDefDecl subst supplied surface surfaceGrp surplus table tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textDesc time title titlePage titlePart titleStmt trailer transpose typeDesc typeNote unclear undo val value w xenoData zone | ||||||||||||||||||||||||||||||||||||||||||||
| Attributes | Attributes att.global.rendition (@rendition) att.global.linking (@corresp, @sameAs, @next, @prev) att.global.analytic (@ana) att.global.facs (@facs) att.global.change (@change) att.global.responsibility (@cert, @resp)
| ||||||||||||||||||||||||||||||||||||||||||||
6.3.17. att.global.analytic
| att.global.analytic provides additional global attributes for associating specific analyses or interpretations with appropriate portions of a text. [17.3. Spans and Interpretations] | |||||||||
| Module | analysis | ||||||||
| Members | att.global[TEI ab abbr abstract actor add addSpan addrLine address am anchor appInfo application argument att author authority availability back bibl biblFull biblScope biblStruct body byline c cRefPattern calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change charDecl charProp choice cit classCode classDecl closer corr correction correspAction correspContext correspDesc creation damage damageSpan date dateline del desc distributor div docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email encodingDesc epigraph ex expan extent facsimile figDesc figure fileDesc floatingText foreign formula front funder fw g gap geoDecl gi glyph glyphName graphic group handNote handShift head hi hyphenation idno imprimatur imprint interpretation item keywords l label langUsage language lb lg licence line list listBibl listChange listPerson listPrefixDef listTranspose localName measure metamark milestone mod monogr msDesc msIdentifier name namespace normalization note notesStmt num opener orig p pb pc person physDesc postscript prefixDef principal profileDesc projectDesc pubPlace publicationStmt publisher punctuation q quotation quote redo ref refState refsDecl reg relatedItem rendition repository resp respStmt restore retrace revisionDesc rhyme role roleDesc row rs s salute samplingDecl scriptNote seg segmentation seriesStmt sic signed sourceDesc sourceDoc sp spGrp speaker sponsor stage stdVals styleDefDecl subst supplied surface surfaceGrp surplus table tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textDesc time title titlePage titlePart titleStmt trailer transpose typeDesc typeNote unclear undo val value w xenoData zone] | ||||||||
| Attributes | Attributes
| ||||||||
6.3.18. att.global.change
| att.global.change supplies the change attribute, allowing its member elements to specify one or more states or revision campaigns with which they are associated. | |||||||
| Module | transcr | ||||||
| Members | att.global[TEI ab abbr abstract actor add addSpan addrLine address am anchor appInfo application argument att author authority availability back bibl biblFull biblScope biblStruct body byline c cRefPattern calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change charDecl charProp choice cit classCode classDecl closer corr correction correspAction correspContext correspDesc creation damage damageSpan date dateline del desc distributor div docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email encodingDesc epigraph ex expan extent facsimile figDesc figure fileDesc floatingText foreign formula front funder fw g gap geoDecl gi glyph glyphName graphic group handNote handShift head hi hyphenation idno imprimatur imprint interpretation item keywords l label langUsage language lb lg licence line list listBibl listChange listPerson listPrefixDef listTranspose localName measure metamark milestone mod monogr msDesc msIdentifier name namespace normalization note notesStmt num opener orig p pb pc person physDesc postscript prefixDef principal profileDesc projectDesc pubPlace publicationStmt publisher punctuation q quotation quote redo ref refState refsDecl reg relatedItem rendition repository resp respStmt restore retrace revisionDesc rhyme role roleDesc row rs s salute samplingDecl scriptNote seg segmentation seriesStmt sic signed sourceDesc sourceDoc sp spGrp speaker sponsor stage stdVals styleDefDecl subst supplied surface surfaceGrp surplus table tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textDesc time title titlePage titlePart titleStmt trailer transpose typeDesc typeNote unclear undo val value w xenoData zone] | ||||||
| Attributes | Attributes
| ||||||
6.3.19. att.global.facs
| att.global.facs groups elements corresponding with all or part of an image, because they contain an alternative representation of it, typically but not necessarily a transcription of it. [11.1. Digital Facsimiles] | |||||||
| Module | transcr | ||||||
| Members | att.global[TEI ab abbr abstract actor add addSpan addrLine address am anchor appInfo application argument att author authority availability back bibl biblFull biblScope biblStruct body byline c cRefPattern calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change charDecl charProp choice cit classCode classDecl closer corr correction correspAction correspContext correspDesc creation damage damageSpan date dateline del desc distributor div docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email encodingDesc epigraph ex expan extent facsimile figDesc figure fileDesc floatingText foreign formula front funder fw g gap geoDecl gi glyph glyphName graphic group handNote handShift head hi hyphenation idno imprimatur imprint interpretation item keywords l label langUsage language lb lg licence line list listBibl listChange listPerson listPrefixDef listTranspose localName measure metamark milestone mod monogr msDesc msIdentifier name namespace normalization note notesStmt num opener orig p pb pc person physDesc postscript prefixDef principal profileDesc projectDesc pubPlace publicationStmt publisher punctuation q quotation quote redo ref refState refsDecl reg relatedItem rendition repository resp respStmt restore retrace revisionDesc rhyme role roleDesc row rs s salute samplingDecl scriptNote seg segmentation seriesStmt sic signed sourceDesc sourceDoc sp spGrp speaker sponsor stage stdVals styleDefDecl subst supplied surface surfaceGrp surplus table tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textDesc time title titlePage titlePart titleStmt trailer transpose typeDesc typeNote unclear undo val value w xenoData zone] | ||||||
| Attributes | Attributes
| ||||||
6.3.20. att.global.linking
| att.global.linking defines a set of attributes for hypertextual linking. | |||||||||||||||||||||||||||||
| Module | linking | ||||||||||||||||||||||||||||
| Members | att.global[TEI ab abbr abstract actor add addSpan addrLine address am anchor appInfo application argument att author authority availability back bibl biblFull biblScope biblStruct body byline c cRefPattern calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change charDecl charProp choice cit classCode classDecl closer corr correction correspAction correspContext correspDesc creation damage damageSpan date dateline del desc distributor div docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email encodingDesc epigraph ex expan extent facsimile figDesc figure fileDesc floatingText foreign formula front funder fw g gap geoDecl gi glyph glyphName graphic group handNote handShift head hi hyphenation idno imprimatur imprint interpretation item keywords l label langUsage language lb lg licence line list listBibl listChange listPerson listPrefixDef listTranspose localName measure metamark milestone mod monogr msDesc msIdentifier name namespace normalization note notesStmt num opener orig p pb pc person physDesc postscript prefixDef principal profileDesc projectDesc pubPlace publicationStmt publisher punctuation q quotation quote redo ref refState refsDecl reg relatedItem rendition repository resp respStmt restore retrace revisionDesc rhyme role roleDesc row rs s salute samplingDecl scriptNote seg segmentation seriesStmt sic signed sourceDesc sourceDoc sp spGrp speaker sponsor stage stdVals styleDefDecl subst supplied surface surfaceGrp surplus table tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textDesc time title titlePage titlePart titleStmt trailer transpose typeDesc typeNote unclear undo val value w xenoData zone] | ||||||||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||||||||
6.3.21. att.global.rendition
| att.global.rendition provides rendering attributes common to all elements in the TEI encoding scheme. | |||||||||||||
| Module | tei | ||||||||||||
| Members | att.global[TEI ab abbr abstract actor add addSpan addrLine address am anchor appInfo application argument att author authority availability back bibl biblFull biblScope biblStruct body byline c cRefPattern calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change charDecl charProp choice cit classCode classDecl closer corr correction correspAction correspContext correspDesc creation damage damageSpan date dateline del desc distributor div docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email encodingDesc epigraph ex expan extent facsimile figDesc figure fileDesc floatingText foreign formula front funder fw g gap geoDecl gi glyph glyphName graphic group handNote handShift head hi hyphenation idno imprimatur imprint interpretation item keywords l label langUsage language lb lg licence line list listBibl listChange listPerson listPrefixDef listTranspose localName measure metamark milestone mod monogr msDesc msIdentifier name namespace normalization note notesStmt num opener orig p pb pc person physDesc postscript prefixDef principal profileDesc projectDesc pubPlace publicationStmt publisher punctuation q quotation quote redo ref refState refsDecl reg relatedItem rendition repository resp respStmt restore retrace revisionDesc rhyme role roleDesc row rs s salute samplingDecl scriptNote seg segmentation seriesStmt sic signed sourceDesc sourceDoc sp spGrp speaker sponsor stage stdVals styleDefDecl subst supplied surface surfaceGrp surplus table tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textDesc time title titlePage titlePart titleStmt trailer transpose typeDesc typeNote unclear undo val value w xenoData zone] | ||||||||||||
| Attributes | Attributes
| ||||||||||||
| Schematron |
<s:rule context="tei:*[@rendition]">
<s:let name="results"
value="for $val in tokenize(normalize-space(@rendition),'\s+') return
starts-with($val,'simple:') or (starts-with($val,'#')
and //tei:rendition[@xml:id=substring($val,2)])"/>
<s:assert test="every $x in $results satisfies $x"> Error: Each of the rendition values in "<s:value-of select="@rendition"/>" must point to a local ID or to a token in the Simple scheme (<s:value-of select="$results"/>)</s:assert></s:rule> | ||||||||||||
| Schematron |
<s:rule context="tei:*[@corresp]">
<s:let name="results"
value="for $t in tokenize(normalize-space(@corresp),'\s+') return
starts-with($t,'#') and not(id(substring($t,2)))"/>
<s:report test="some $x in $results satisfies $x"> Error: Every local pointer in "<s:value-of select="@corresp"/>" must point to an ID in this document (<s:value-of select="$results"/>)</s:report></s:rule> | ||||||||||||
6.3.22. att.global.responsibility
| att.global.responsibility provides attributes indicating the agency responsible for some aspect of the text, the markup or something asserted by the markup, and the degree of certainty associated with it. [3.4. Simple Editorial Changes 11.3.2.2. Hand, Responsibility, and Certainty Attributes 17.3. Spans and Interpretations 13.1.1. Linking Names and Their Referents] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.global[TEI ab abbr abstract actor add addSpan addrLine address am anchor appInfo application argument att author authority availability back bibl biblFull biblScope biblStruct body byline c cRefPattern calendar calendarDesc castGroup castItem castList catDesc catRef category cb cell change charDecl charProp choice cit classCode classDecl closer corr correction correspAction correspContext correspDesc creation damage damageSpan date dateline del desc distributor div docAuthor docDate docEdition docImprint docTitle edition editionStmt editor editorialDecl email encodingDesc epigraph ex expan extent facsimile figDesc figure fileDesc floatingText foreign formula front funder fw g gap geoDecl gi glyph glyphName graphic group handNote handShift head hi hyphenation idno imprimatur imprint interpretation item keywords l label langUsage language lb lg licence line list listBibl listChange listPerson listPrefixDef listTranspose localName measure metamark milestone mod monogr msDesc msIdentifier name namespace normalization note notesStmt num opener orig p pb pc person physDesc postscript prefixDef principal profileDesc projectDesc pubPlace publicationStmt publisher punctuation q quotation quote redo ref refState refsDecl reg relatedItem rendition repository resp respStmt restore retrace revisionDesc rhyme role roleDesc row rs s salute samplingDecl scriptNote seg segmentation seriesStmt sic signed sourceDesc sourceDoc sp spGrp speaker sponsor stage stdVals styleDefDecl subst supplied surface surfaceGrp surplus table tag tagUsage tagsDecl taxonomy teiCorpus teiHeader term text textClass textDesc time title titlePage titlePart titleStmt trailer transpose typeDesc typeNote unclear undo val value w xenoData zone] | ||||||||||||||
| Attributes | Attributes
| ||||||||||||||
| Example | Blessed are the
<choice>
<sic>placemakers</sic>
<corr resp="#editor" cert="high">peacemakers</corr>
</choice>: for they shall be called the children of God. | ||||||||||||||
| Example |
<!-- in the <text> ... --><lg>
<!-- ... -->
<l>Punkes, Panders, baſe extortionizing
sla<choice>
<sic>n</sic>
<corr resp="#JENS1_transcriber">u</corr>
</choice>es,</l>
<!-- ... -->
</lg>
<!-- in the <teiHeader> ... -->
<!-- ... -->
<respStmt xml:id="JENS1_transcriber">
<resp when="2014">Transcriber</resp>
<name>Janelle Jenstad</name>
</respStmt> | ||||||||||||||
6.3.23. att.handFeatures
| att.handFeatures provides attributes describing aspects of the hand in which a manuscript is written. [11.3.2.1. Document Hands] | |||||||||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||||||||
| Members | handNote handShift scriptNote typeNote | ||||||||||||||||||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||||||||||||||||||
| Note | Usually either script or scriptRef, and similarly, either scribe or scribeRef, will be supplied. | ||||||||||||||||||||||||||||||||||||||
6.3.24. att.internetMedia
| att.internetMedia provides attributes for specifying the type of a computer resource using a standard taxonomy. | |||||||
| Module | tei | ||||||
| Members | att.media[graphic] ref | ||||||
| Attributes | Attributes
| ||||||
| Example | In this example mimeType is used to indicate that the URL points to a TEI XML file encoded in UTF-8. <ref mimeType="application/tei+xml; charset=UTF-8"
target="http://sourceforge.net/p/tei/code/HEAD/tree/trunk/P5/Source/guidelines-en.xml"/> | ||||||
| Note | This attribute class provides an attribute for describing a computer resource, typically available over the internet, using a value taken from a standard taxonomy. At present only a single taxonomy is supported, the Multipurpose Internet Mail Extensions (MIME) Media Type system. This typology of media types is defined by the Internet Engineering Task Force in RFC 2046. The list of types is maintained by the Internet Assigned Numbers Authority (IANA). The mimeType attribute must have a value taken from this list. | ||||||
6.3.25. att.measurement
| att.measurement provides attributes to represent a regularized or normalized measurement. | |||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||
| Members | measure | ||||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||||
| Note | This attribute class provides a triplet of attributes that may be used either to regularize the values of the measurement being encoded, or to normalize them with respect to a standard measurement system. <l>So weren't you gonna buy <measure quantity="0.5" unit="gal"
commodity="ice cream">half
a gallon</measure>, baby</l>
<l>So won't you go and buy <measure quantity="1.893" unit="L"
commodity="ice cream">half
a gallon</measure>, baby?</l> | ||||||||||||||||||||||||
| Note | The unit should normally be named using the standard abbreviation for an SI unit (see further http://www.bipm.org/en/publications/si-brochure/; http://physics.nist.gov/cuu/Units/). However, encoders may also specify measurements using informally defined units such as lines or characters. | ||||||||||||||||||||||||
6.3.26. att.media
| att.media provides attributes for specifying display and related properties of external media. | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | graphic | ||||||||||||||||||
| Attributes | Attributes att.internetMedia (@mimeType)
| ||||||||||||||||||
6.3.27. att.milestoneUnit
| att.milestoneUnit provides an attribute to indicate the type of section which is changing at a specific milestone. [3.10.3. Milestone Elements 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration] | |||||||||||||
| Module | core | ||||||||||||
| Members | milestone refState | ||||||||||||
| Attributes | Attributes
| ||||||||||||
6.3.28. att.naming
| att.naming provides attributes common to elements which refer to named persons, places, organizations etc. [3.5.1. Referring Strings 13.3.5. Names and Nyms] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | att.personal[name] author editor pubPlace repository rs | ||||||||||||||
| Attributes | Attributes att.canonical (@key, @ref)
| ||||||||||||||
6.3.29. att.patternReplacement
| att.patternReplacement provides attributes for regular-expression matching and replacement. [16.2.3. Using Abbreviated Pointers 2.3.6.3. Milestone Method 2.3.6. The Reference System Declaration 2.3.6.2. Search-and-Replace Method] | |||||||||||||||||
| Module | header | ||||||||||||||||
| Members | cRefPattern prefixDef | ||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||
6.3.30. att.personal
| att.personal (attributes for components of names usually, but not necessarily, personal names) common attributes for those elements which form part of a name usually, but not necessarily, a personal name. [13.2.1. Personal Names] | |||||||||||||||
| Module | tei | ||||||||||||||
| Members | name | ||||||||||||||
| Attributes | Attributes att.naming (@role, @nymRef) (att.canonical (@key, @ref))
| ||||||||||||||
6.3.31. att.placement
| att.placement provides attributes for describing where on the source page or object a textual element appears. | |||||||||||||
| Module | tei | ||||||||||||
| Members | add addSpan figure fw label metamark note stage | ||||||||||||
| Attributes | Attributes
| ||||||||||||
6.3.32. att.pointing
| att.pointing defines a set of attributes used by all elements which point to other elements by means of one or more URI references. | |||||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||||
| Members | calendar catRef licence note ref term | ||||||||||||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||||||||||||
6.3.33. att.ranging
| att.ranging provides attributes for describing numerical ranges. | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | att.dimensions[att.damaged[damage damageSpan] att.editLike[att.transcriptional[add addSpan del mod redo restore retrace subst undo] am corr date ex expan gap name person reg supplied surplus time unclear] space] num | ||||||||||||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||||||||||||
| Example | The MS. was lost in transmission by mail from <del rend="overstrike">
<gap reason="illegible"
extent="one or two letters" atLeast="1" atMost="2" unit="chars"/>
</del> Philadelphia to the Graphic office, New York.
| ||||||||||||||||||||||||||||||
6.3.34. att.resourced
| att.resourced provides attributes by which a resource (such as an externally held media file) may be located. | |||||||
| Module | tei | ||||||
| Members | graphic | ||||||
| Attributes | Attributes
| ||||||
6.3.35. att.segLike
| att.segLike provides attributes for elements used for arbitrary segmentation. [16.3. Blocks, Segments, and Anchors 17.1. Linguistic Segment Categories] | |||||||||
| Module | tei | ||||||||
| Members | c pc s seg w | ||||||||
| Attributes | Attributes att.fragmentable (@part)
| ||||||||
6.3.36. att.sortable
| att.sortable provides attributes for elements in lists or groups that are sortable, but whose sorting key cannot be derived mechanically from the element content. [9.1. Dictionary Body and Overall Structure] | |||||||||||
| Module | tei | ||||||||||
| Members | bibl biblFull biblStruct correspAction idno item list listBibl listChange listPerson msDesc person term | ||||||||||
| Attributes | Attributes
| ||||||||||
6.3.37. att.source
| att.source provides attributes for pointing to the source of a bibliographic reference. [3.3.3. Quotation 8.3.4. Writing] | |||||||
| Module | tei | ||||||
| Members | att.editLike[att.transcriptional[add addSpan del mod redo restore retrace subst undo] am corr date ex expan gap name person reg supplied surplus time unclear] abbr abstract handShift note orig q quote rs seg sic space | ||||||
| Attributes | Attributes
| ||||||
| Example | <p>
<!-- ... -->
As Willard McCarty (<bibl xml:id="mcc_2012">2012, p.2</bibl>)
tells us, <quote source="#mcc_2012">‘Collaboration’ is a
problematic and should be a contested term.</quote>
<!-- ... -->
</p> | ||||||
| Example | <p>
<!-- ... -->
<quote source="#chicago_15_ed">Grammatical theories
are in flux, and the more we learn, the less we
seem to know.</quote>
<!-- ... -->
</p>
<!-- ... -->
<bibl xml:id="chicago_15_ed">
<title level="m">The Chicago Manual of Style</title>,
<edition>15th edition</edition>.
<pubPlace>Chicago</pubPlace>:
<publisher>University of Chicago Press</publisher>
(<date>2003</date>),
<biblScope unit="page">p.147</biblScope>.
</bibl> | ||||||
6.3.38. att.spanning
| att.spanning provides attributes for elements which delimit a span of text by pointing mechanisms rather than by enclosing it. [1.3.1. Attribute Classes] | |||||||||
| Module | tei | ||||||||
| Members | addSpan cb damageSpan lb metamark milestone mod pb redo retrace undo | ||||||||
| Attributes | Attributes
| ||||||||
| Note | The span is defined as running in document order from the start of the content of the pointing element to the end of the content of the element pointed to by the spanTo attribute (if any). If no value is supplied for the attribute, the assumption is that the span is coextensive with the pointing element. If no content is present, the assumption is that the starting point of the span is immediately following the element itself. | ||||||||
6.3.39. att.styleDef
| att.styleDef groups elements which specify the name of a formal definition language used to provide formatting or rendition information. | |||||||||||||||||||||
| Module | tei | ||||||||||||||||||||
| Members | rendition styleDefDecl | ||||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||||
6.3.40. att.transcriptional
| att.transcriptional provides attributes specific to elements encoding authorial or scribal intervention in a text when transcribing manuscript or similar sources. [11.3.1.4. Additions and Deletions] | |||||||||||||||||||||||||||||||
| Module | tei | ||||||||||||||||||||||||||||||
| Members | add addSpan del mod redo restore retrace subst undo | ||||||||||||||||||||||||||||||
| Attributes | Attributes att.editLike (@evidence, @instant) (att.dimensions (@unit, @quantity, @extent, @precision, @scope) (att.ranging (@atLeast, @atMost, @min, @max, @confidence)) ) (att.source (@source))
| ||||||||||||||||||||||||||||||
6.3.41. att.translatable
| att.translatable provides attributes used to indicate the status of a translatable portion of an ODD document. | |||||||||
| Module | tei | ||||||||
| Members | desc | ||||||||
| Attributes | Attributes
| ||||||||
6.3.42. att.typed
| att.typed provides attributes which can be used to classify or subclassify elements in any way. [1.3.1. Attribute Classes 17.1.1. Words and Above 3.5.1. Referring Strings 3.6. Simple Links and Cross-References 3.5.5. Abbreviations and Their Expansions 3.12.1. Core Tags for Verse 7.2.5. Speech Contents 4.1.1. Un-numbered Divisions 4.1.2. Numbered Divisions 4.2.1. Headings and Trailers 4.4. Virtual Divisions 13.3.2.3. Personal Relationships 11.3.1.1. Core Elements for Transcriptional Work 16.1.1. Pointers and Links 16.3. Blocks, Segments, and Anchors 12.2. Linking the Apparatus to the Text 22.4.4.2. RELAX NG Content Models 8.3. Elements Unique to Spoken Texts 23.3.1.4. Modification of Attribute and Attribute Value Lists] | |||||||||||||||||||
| Module | tei | ||||||||||||||||||
| Members | ab add addSpan am anchor application bibl biblStruct c cb change charProp cit corr correspDesc damage damageSpan date del desc div figure floatingText g group head label lb lg line listBibl listPerson milestone mod msDesc note pb pc quote ref reg relatedItem restore rhyme rs s seg spGrp space surface surfaceGrp term text time trailer w xenoData zone | ||||||||||||||||||
| Attributes | Attributes
| ||||||||||||||||||
| Schematron |
<sch:rule context="*[@subtype]">
<sch:assert test="@type">The <sch:name/> element should not be categorized in detail with @subtype
unless also categorized in general with @type</sch:assert></sch:rule> | ||||||||||||||||||
| Note | When appropriate, values from an established typology should be used. Alternatively a typology may be defined in the associated TEI header. If values are to be taken from a project-specific list, this should be defined using the <valList> element in the project-specific schema description, as described in 23.3.1.4. Modification of Attribute and Attribute Value Lists . | ||||||||||||||||||
6.4. Macros
6.4.1. data.certainty
| data.certainty defines the range of attribute values expressing a degree of certainty. | |
| Module | tei |
| Used by | |
| Declaration | data.certainty = "high" | "medium" | "low" | "unknown" |
| Note | Certainty may be expressed by one of the predefined symbolic values high, medium, or low. The value unknown should be used in cases where the encoder does not wish to assert an opinion about the matter. For more precise indication, data.probability may be used instead or in addition. |
6.4.2. data.count
| data.count defines the range of attribute values used for a non-negative integer value used as a count. | |
| Module | tei |
| Used by | |
| Declaration | data.count = xsd:nonNegativeInteger |
| Note | Only positive integer values (including zero) are permitted |
6.4.3. data.duration.iso
| data.duration.iso defines the range of attribute values available for representation of a duration in time using ISO 8601 standard formats | |
| Module | tei |
| Used by | |
| Declaration |
data.duration.iso = token { pattern = "[0-9.,DHMPRSTWYZ/:+\-]+" } |
| Example | <time dur-iso="PT0,75H">three-quarters of an hour</time> |
| Example | <date dur-iso="P1,5D">a day and a half</date> |
| Example | <date dur-iso="P14D">a fortnight</date> |
| Example | <time dur-iso="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the last, which may have a decimal component (using either . or , as the decimal point; the latter is preferred). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.For complete details, see ISO 8601 Data elements and interchange formats — Information interchange — Representation of dates and times. |
6.4.4. data.duration.w3c
| data.duration.w3c defines the range of attribute values available for representation of a duration in time using W3C datatypes. | |
| Module | tei |
| Used by | |
| Declaration | data.duration.w3c = xsd:duration |
| Example | <time dur="PT45M">forty-five minutes</time> |
| Example | <date dur="P1DT12H">a day and a half</date> |
| Example | <date dur="P7D">a week</date> |
| Example | <time dur="PT0.02S">20 ms</time> |
| Note | A duration is expressed as a sequence of number-letter pairs, preceded by the letter P; the letter gives the unit and may be Y (year), M (month), D (day), H (hour), M (minute), or S (second), in that order. The numbers are all unsigned integers, except for the S number, which may have a decimal component (using . as the decimal point). If any number is 0, then that number-letter pair may be omitted. If any of the H (hour), M (minute), or S (second) number-letter pairs are present, then the separator T must precede the first ‘time’ number-letter pair.For complete details, see the W3C specification. |
6.4.5. data.enumerated
| data.enumerated defines the range of attribute values expressed as a single XML name taken from a list of documented possibilities. | |
| Module | tei |
| Used by | Element:
|
| Declaration | data.enumerated = data.word |
| Note | Attributes using this datatype must contain a single word matching the pattern defined for this datatype: for example it cannot include whitespace but may begin with digits. Typically, the list of documented possibilities will be provided (or exemplified) by a value list in the associated attribute specification, expressed with a <valList> element. |
6.4.6. data.language
| data.language defines the range of attribute values used to identify a particular combination of human language and writing system. [6.1. Language Identification] | |
| Module | tei |
| Used by | Element:
|
| Declaration | data.language = xsd:language | "" |
| Note | The values for this attribute are language ‘tags’ as defined in BCP 47. Currently BCP 47 comprises RFC 5646 and RFC 4647; over time, other IETF documents may succeed these as the best current practice.A ‘language tag’, per BCP 47, is assembled from a sequence of components or subtags separated by the hyphen character (-, U+002D). The tag is made of the following subtags, in the following order. Every subtag except the first is optional. If present, each occurs only once, except the fourth and fifth components (variant and extension), which are repeatable.
There are two exceptions to the above format. First, there are language tags in the IANA registry that do not match the above syntax, but are present because they have been ‘grandfathered’ from previous specifications. Second, an entire language tag can consist of only a private use subtag. These tags start with x-, and do not need to follow any further rules established by the IETF and endorsed by these Guidelines. Like all language tags that make use of private use subtags, the language in question must be documented in a corresponding <language> element in the TEI header.Examples include
The W3C Internationalization Activity has published a useful introduction to BCP 47, Language tags in HTML and XML. |
6.4.7. data.name
| data.name defines the range of attribute values expressed as an XML Name. | |
| Module | tei |
| Used by | |
| Declaration | data.name = xsd:Name |
| Note | Attributes using this datatype must contain a single word which follows the rules defining a legal XML name (see http://www.w3.org/TR/REC-xml/#dt-name): for example they cannot include whitespace or begin with digits. |
6.4.8. data.namespace
| data.namespace defines the range of attribute values used to indicate XML namespaces as defined by the W3C Namespaces in XML Technical Recommendation. | |
| Module | tei |
| Used by | Element:
|
| Declaration | data.namespace = xsd:anyURI |
| Note | The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax |
6.4.9. data.numeric
| data.numeric defines the range of attribute values used for numeric values. | |
| Module | tei |
| Used by | Element:
|
| Declaration |
data.numeric =
xsd:double | token { pattern = "(\-?[\d]+/\-?[\d]+)" } | xsd:decimal |
| Note | Any numeric value, represented as a decimal number, in floating point format, or as a ratio.To represent a floating point number, expressed in scientific notation, ‘E notation’, a variant of ‘exponential notation’, may be used. In this format, the value is expressed as two numbers separated by the letter E. The first number, the significand (sometimes called the mantissa) is given in decimal format, while the second is an integer. The value is obtained by multiplying the mantissa by 10 the number of times indicated by the integer. Thus the value represented in decimal notation as 1000.0 might be represented in scientific notation as 10E3. A value expressed as a ratio is represented by two integer values separated by a solidus (/) character. Thus, the value represented in decimal notation as 0.5 might be represented as a ratio by the string 1/2. |
6.4.10. data.outputMeasurement
| data.outputMeasurement defines a range of values for use in specifying the size of an object that is intended for display. | |
| Module | tei |
| Used by | |
| Declaration |
data.outputMeasurement =
token
{
pattern = "[\-+]?\d+(\.\d+)?(%|cm|mm|in|pt|pc|px|em|ex|gd|rem|vw|vh|vm)"
} |
| Example | <figure>
<head>The TEI Logo</head>
<figDesc>Stylized yellow angle brackets with the letters <mentioned>TEI</mentioned> in
between and <mentioned>text encoding initiative</mentioned> underneath, all on a white
background.</figDesc>
<graphic height="600px" width="600px"
url="http://www.tei-c.org/logos/TEI-600.jpg"/>
</figure> |
| Note | These values map directly onto the values used by XSL-FO and CSS. For definitions of the units see those specifications; at the time of this writing the most complete list is in the CSS3 working draft. |
6.4.11. data.pattern
| data.pattern (regular expression pattern) defines attribute values which are expressed as a regular expression. | |
| Module | tei |
| Used by | |
| Declaration | data.pattern = token |
| Note | A regular expression, often called a pattern, is an expression that describes a set of strings. They are usually used to give a concise description of a set, without having to list all elements. For example, the set containing the three strings Handel, Händel, and Haendel can be described by the pattern WikipediaH(ä|ae?)ndel (or alternatively, it is said that the pattern H(ä|ae?)ndel matches each of the three strings) |
6.4.12. data.point
| data.point defines the data type used to express a point in cartesian space. | |
| Module | tei |
| Used by | |
| Declaration |
data.point = token { pattern = "(\-?[0-9]+\.?[0-9]*,\-?[0-9]+\.?[0-9]*)" } |
| Example | <facsimile>
<surface ulx="0" uly="0" lrx="400" lry="280">
<zone points="220,100 300,210 170,250 123,234">
<graphic url="handwriting.png "/>
</zone>
</surface>
</facsimile> |
| Note | A point is defined by two numeric values, which may be expressed in any notation permitted. |
6.4.13. data.pointer
| data.pointer defines the range of attribute values used to provide a single URI, absolute or relative, pointing to some other resource, either within the current document or elsewhere. | |
| Module | tei |
| Used by | |
| Declaration | data.pointer = xsd:anyURI |
| Note | The range of syntactically valid values is defined by RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. Note that the values themselves are encoded using RFC 3987 Internationalized Resource Identifiers (IRIs) mapping to URIs. For example, https://secure.wikimedia.org/wikipedia/en/wiki/% is encoded as https://secure.wikimedia.org/wikipedia/en/wiki/%25 while http://موقع.وزارة-الاتصالات.مصر/ is encoded as http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/ |
6.4.14. data.probability
| data.probability defines the range of attribute values expressing a probability. | |
| Module | tei |
| Used by | |
| Declaration |
data.probability = xsd:double { minInclusive = "0" maxInclusive = "1" } |
| Note | Probability is expressed as a real number between 0 and 1; 0 representing certainly false and 1 representing certainly true. |
6.4.15. data.replacement
| data.replacement defines attribute values which contain a replacement template. | |
| Module | tei |
| Used by | |
| Declaration | data.replacement = text |
6.4.16. data.sex
| data.sex defines the range of attribute values used to identify human or animal sex. | |
| Module | tei |
| Used by | Element:
|
| Declaration | data.sex = data.word |
| Note | Values for attributes using this datatype may be locally defined by a project, or may refer to an external standard, such as vCard's sex property http://microformats.org/wiki/gender-formats (in which M indicates male, F female, O other, N none or not applicable, U unknown), or the often used ISO 5218:2004 Representation of Human Sexes http://standards.iso.org/ittf/PubliclyAvailableStandards/c036266_ISO_IEC_5218_2004(E_F).zip (in which 0 indicates unknown; 1 male; 2 female; and 9 not applicable, although the ISO standard is widely considered inadequate); cf. CETH's Recommendations for Inclusive Data Collection of Trans People http://transhealth.ucsf.edu/trans?page=lib-data-collection. |
6.4.17. data.temporal.w3c
| data.temporal.w3c defines the range of attribute values expressing a temporal expression such as a date, a time, or a combination of them, that conform to the W3C XML Schema Part 2: Datatypes Second Edition specification. | |
| Module | tei |
| Used by | Element:
|
| Declaration | data.temporal.w3c = xsd:date | xsd:gYear | xsd:gMonth | xsd:gDay | xsd:gYearMonth | xsd:gMonthDay | xsd:time | xsd:dateTime |
| Note | If it is likely that the value used is to be compared with another, then a time zone indicator should always be included, and only the dateTime representation should be used. |
6.4.18. data.text
| data.text defines the range of attribute values used to express some kind of identifying string as a single sequence of unicode characters possibly including whitespace. | |
| Module | tei |
| Used by | |
| Declaration | data.text = string |
| Note | Attributes using this datatype must contain a single ‘token’ in which whitespace and other punctuation characters are permitted. |
6.4.19. data.truthValue
| data.truthValue defines the range of attribute values used to express a truth value. | |
| Module | tei |
| Used by | Element:
|
| Declaration | data.truthValue = xsd:boolean |
| Note | The possible values of this datatype are 1 or true, or 0 or false.This datatype applies only for cases where uncertainty is inappropriate; if the attribute concerned may have a value other than true or false, e.g. unknown, or inapplicable, it should have the extended version of this datatype: data.xTruthValue. |
6.4.20. data.version
| data.version defines the range of attribute values which may be used to specify a TEI or Unicode version number. | |
| Module | tei |
| Used by | |
| Declaration |
data.version = token { pattern = "[\d]+(\.[\d]+){0,2}" } |
| Note | The value of this attribute follows the pattern specified by the Unicode consortium for its version number (http://unicode.org/versions/). A version number contains digits and fullstop characters only. The first number supplied identifies the major version number. A second and third number, for minor and sub-minor version numbers, may also be supplied. |
6.4.21. data.versionNumber
| data.versionNumber defines the range of attribute values used for version numbers. | |
| Module | tei |
| Used by | Element:
|
| Declaration |
data.versionNumber =
token { pattern = "[\d]+[a-z]*[\d]*(\.[\d]+[a-z]*[\d]*){0,3}" } |
6.4.22. data.word
| data.word defines the range of attribute values expressed as a single word or token. | |
| Module | tei |
| Used by | |
| Declaration |
data.word = token { pattern = "(\p{L}|\p{N}|\p{P}|\p{S})+" } |
| Note | Attributes using this datatype must contain a single ‘word’ which contains only letters, digits, punctuation characters, or symbols: thus it cannot include whitespace. |
6.4.23. data.xTruthValue
| data.xTruthValue (extended truth value) defines the range of attribute values used to express a truth value which may be unknown. | |
| Module | tei |
| Used by | |
| Declaration | data.xTruthValue = xsd:boolean | "unknown" | "inapplicable" |
| Note | In cases where where uncertainty is inappropriate, use the datatype data.TruthValue. |
6.4.24. macro.anyXML
| macro.anyXML defines a content model within which any XML elements are permitted | |
| Module | tei |
| Used by | |
| Declaration |
macro.anyXML =
element * - (tei:* | teix:egXML)
{
attribute * { text }*,
( text | macro.anyXML )*
} |
6.4.25. macro.limitedContent
| macro.limitedContent (paragraph content) defines the content of prose elements that are not used for transcription of extant materials. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Declaration | macro.limitedContent = ( text | model.limitedPhrase | model.inter )* |
6.4.26. macro.paraContent
| macro.paraContent (paragraph content) defines the content of paragraphs and similar elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Declaration |
macro.paraContent =
(
text
| model.gLike
| model.phrase
| model.inter
| model.global
| lg
| model.lLike
)* |
6.4.27. macro.phraseSeq
| macro.phraseSeq (phrase sequence) defines a sequence of character data and phrase-level elements. [1.4.1. Standard Content Models] | |
| Module | tei |
| Used by | |
| Declaration | macro.phraseSeq = ( text | model.gLike | model.phrase | model.global )* |
6.4.28. macro.phraseSeq.limited
| macro.phraseSeq.limited (limited phrase sequence) defines a sequence of character data and those phrase-level elements that are not typically used for transcribing extant documents. [1.4.1. Standard Content Models] | |
| Module | tei |
| Used by | |
| Declaration | macro.phraseSeq.limited = ( text | model.limitedPhrase | model.global )* |
6.4.29. macro.specialPara
| macro.specialPara ('special' paragraph content) defines the content model of elements such as notes or list items, which either contain a series of component-level elements or else have the same structure as a paragraph, containing a series of phrase-level and inter-level elements. [1.3. The TEI Class System] | |
| Module | tei |
| Used by | |
| Declaration |
macro.specialPara =
(
text
| model.gLike
| model.phrase
| model.inter
| model.divPart
| model.global
)* |
6.4.30. macro.xtext
| macro.xtext (extended text) defines a sequence of character data and gaiji elements. | |
| Module | tei |
| Used by | |
| Declaration | macro.xtext = ( text | model.gLike )* |
6.5. Summary
A total of 105 elements are selected for use in the <text> part of a document; an additional 44 elements are allowed for in the header. The following table shows the usage of all elements in six existing corpora, and classifies them 11 usage groups. There are 15 elements listed which are not allowed in TEI Simple, but should be transformed to another element.
| Element | dbnl | obvil | cesr | ota | dta | TCP | Group | Use instead |
| TEI | 10172 | 126 | 50 | 457 | 848 | 61315 | structure | |
| ab | 0 | 290 | 1022 | 60480 | 0 | 668 | structure | |
| abbr | 0 | 0 | 1482 | 0 | 69 | 533814 | editorial | |
| actor | 0 | 0 | 0 | 0 | 12 | 0 | castlist | |
| add | 0 | 0 | 71 | 65 | 0 | 2441 | editorial | |
| addName | 0 | 0 | 7 | 0 | 0 | 0 | <name> | |
| addSpan | 0 | 0 | 0 | 2 | 0 | 4 | editorial | |
| addrLine | 0 | 0 | 10 | 0 | 0 | 0 | structure | |
| address | 0 | 0 | 5 | 0 | 0 | 0 | structure | |
| am | 0 | 0 | 0 | 0 | 0 | 166291 | editorial | |
| anchor | 0 | 233 | 0 | 29 | 0 | 4 | structure | |
| argument | 0 | 151 | 0 | 57 | 2268 | 71478 | wrapper | |
| att | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| author | 0 | 34 | 83 | 1 | 0 | 0 | interpretation | |
| back | 0 | 1 | 29 | 77 | 608 | 24439 | structure | |
| bibl | 3187 | 274 | 155 | 414 | 4362 | 296835 | structure | |
| biblFull | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| biblScope | 0 | 0 | 4 | 0 | 0 | 0 | header | |
| biblStruct | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| body | 10171 | 126 | 50 | 688 | 1155 | 106968 | structure | |
| byline | 0 | 17 | 8 | 619 | 1028 | 12525 | wrapper | |
| c | 8966 | 0 | 0 | 0 | 0 | 0 | linguistic | |
| caesura | 0 | 0 | 0 | 30299 | 0 | 0 | <milestone/> | |
| castGroup | 0 | 0 | 29 | 0 | 51 | 0 | castlist | |
| castItem | 0 | 0 | 63 | 90 | 744 | 0 | castlist | |
| castList | 0 | 0 | 28 | 4 | 74 | 0 | castlist | |
| cb | 0 | 0 | 66 | 0 | 26294 | 0 | structure | |
| cell | 5895818 | 242 | 3218 | 1282 | 34153 | 3455220 | table | |
| change | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| charDecl | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| charProp | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| choice | 0 | 0 | 61228 | 770 | 8799 | 4106 | editorial | |
| cit | 3209 | 12 | 99 | 155 | 5431 | 0 | structure | |
| closer | 0 | 0 | 35 | 88 | 1430 | 122281 | wrapper | |
| code | 0 | 0 | 0 | 1 | 0 | 0 | <hi> | |
| corr | 0 | 0 | 3103 | 505 | 5966 | 0 | editorial | |
| country | 0 | 0 | 1 | 0 | 0 | 0 | <name> | |
| date | 7842 | 47 | 119 | 61 | 112 | 64488 | interpretation | |
| dateline | 0 | 382 | 1 | 0 | 2264 | 53370 | wrapper | |
| del | 0 | 0 | 62 | 15 | 0 | 7 | editorial | |
| desc | 0 | 186 | 0 | 241 | 0 | 6878050 | editorial | |
| div | 1856262 | 4584 | 2128 | 16744 | 104832 | 1564908 | structure | |
| docAuthor | 0 | 14 | 0 | 381 | 823 | 0 | titlepage | |
| docDate | 0 | 388 | 44 | 6 | 899 | 0 | titlepage | |
| docEdition | 0 | 1 | 0 | 0 | 14 | 0 | titlepage | |
| docImprint | 0 | 0 | 46 | 223 | 946 | 0 | titlepage | |
| docTitle | 0 | 1 | 48 | 349 | 1156 | 0 | titlepage | |
| editor | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| editorialDecl | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| 0 | 0 | 0 | 0 | 0 | 0 | header | ||
| emph | 0 | 1090 | 0 | 6711 | 0 | 0 | <hi> | |
| encodingDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| epigraph | 0 | 2 | 2 | 487 | 137 | 45743 | wrapper | |
| ex | 0 | 0 | 0 | 0 | 0 | 166291 | editorial | |
| expan | 0 | 0 | 1837 | 0 | 69 | 170397 | editorial | |
| extent | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| figDesc | 151116 | 0 | 55 | 87 | 0 | 27314 | pictures | |
| figure | 329174 | 206 | 480 | 227 | 16866 | 95853 | pictures | |
| fileDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| floatingText | 0 | 1 | 0 | 61 | 307 | 40502 | structure | |
| foreign | 0 | 46 | 3348 | 2365 | 1929 | 0 | interpretation | |
| forename | 0 | 1 | 35 | 0 | 0 | 0 | <name> | |
| formula | 0 | 0 | 0 | 0 | 25670 | 0 | structure | |
| front | 13 | 25 | 48 | 380 | 851 | 49991 | structure | |
| fw | 0 | 0 | 20554 | 15 | 336239 | 1268 | structure | |
| g | 0 | 0 | 1012 | 489 | 493 | 915406 | character | |
| gap | 0 | 0 | 18 | 293 | 5731 | 6878505 | editorial | |
| genName | 0 | 0 | 7 | 0 | 0 | 0 | <name> | |
| gi | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| glyph | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| glyphName | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| graphic | 0 | 22 | 362 | 199 | 0 | 0 | pictures | |
| group | 0 | 0 | 0 | 20 | 0 | 2789 | structure | |
| handShift | 0 | 0 | 0 | 0 | 0 | 0 | editorial | |
| head | 1958142 | 4961 | 2526 | 14508 | 117506 | 1811315 | structure | |
| hi | 21179130 | 56953 | 9424 | 134872 | 2367314 | 57472111 | interpretation | |
| idno | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| imprimatur | 0 | 0 | 25 | 23 | 63 | 0 | titlepage | |
| imprint | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| item | 3125926 | 2023 | 1806 | 12400 | 187951 | 3779020 | structure | |
| keywords | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| l | 11532201 | 21004 | 39828 | 268768 | 557846 | 11307818 | structure | |
| label | 483377 | 621 | 469 | 1712 | 0 | 618039 | structure | |
| lb | 1352720 | 3008 | 237202 | 233546 | 9689271 | 24097 | structure | |
| lg | 528349 | 316 | 4481 | 5790 | 84157 | 791590 | structure | |
| licence | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| list | 272365 | 621 | 115 | 526 | 24877 | 407478 | structure | |
| listBibl | 0 | 1 | 0 | 0 | 26 | 0 | structure | |
| listChange | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| listPerson | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| localName | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| measure | 0 | 0 | 0 | 0 | 0 | 0 | interpretation | |
| milestone | 0 | 46 | 13 | 4881 | 49313 | 0 | structure | |
| monogr | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| msDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| msIdentifier | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| name | 536288 | 12265 | 32997 | 2541 | 0 | 0 | interpretation | |
| nameLink | 0 | 0 | 18 | 0 | 0 | 0 | <name> | |
| note | 2705214 | 9451 | 2874 | 4965 | 187675 | 5710304 | structure | |
| num | 0 | 862 | 0 | 0 | 0 | 0 | interpretation | |
| opener | 0 | 0 | 2 | 21 | 513 | 77640 | wrapper | |
| orgName | 0 | 30 | 4607 | 0 | 0 | 0 | <name> | |
| orig | 0 | 0 | 57301 | 274 | 2769 | 0 | editorial | |
| p | 12413479 | 68273 | 4855 | 391507 | 607881 | 11892546 | structure | |
| pb | 2814727 | 6156 | 9497 | 22352 | 311001 | 5424219 | structure | |
| pc | 0 | 0 | 230 | 0 | 0 | 0 | linguistic | |
| persName | 0 | 4045 | 662 | 0 | 26217 | 0 | <name> | |
| person | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| physDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| placeName | 0 | 386 | 11646 | 0 | 18652 | 0 | <name> | |
| postscript | 0 | 17 | 0 | 0 | 133 | 6142 | wrapper | |
| profileDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| ptr | 376134 | 0 | 0 | 180 | 0 | 635 | <ref> | |
| pubPlace | 0 | 0 | 37 | 2 | 918 | 0 | titlepage | |
| publicationStmt | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| publisher | 0 | 2 | 35 | 0 | 910 | 0 | titlepage | |
| q | 212432 | 4270 | 29 | 5829 | 0 | 695548 | interpretation | |
| quote | 0 | 5459 | 270 | 2597 | 5744 | 0 | interpretation | |
| ref | 537332 | 240 | 1119 | 1240 | 140328 | 3541 | interpretation | |
| reg | 442 | 0 | 57311 | 274 | 2765 | 0 | editorial | |
| relatedItem | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| repository | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| resp | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| respStmt | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| rhyme | 0 | 0 | 0 | 0 | 0 | 0 | interpretation | |
| role | 0 | 0 | 33 | 31 | 735 | 0 | castlist | |
| roleDesc | 0 | 0 | 9 | 0 | 70 | 0 | castlist | |
| roleName | 0 | 0 | 70 | 0 | 0 | 0 | <name> | |
| row | 2064752 | 70 | 1311 | 327 | 12571 | 799618 | table | |
| rs | 1 | 5 | 0 | 0 | 0 | 0 | interpretation | |
| s | 1 | 0 | 0 | 0 | 0 | 0 | linguistic | |
| salute | 0 | 11 | 10 | 97 | 2490 | 64544 | wrapper | |
| seg | 46611 | 47 | 0 | 10304 | 0 | 148733 | interpretation | |
| sic | 0 | 0 | 3707 | 534 | 5960 | 0 | editorial | |
| signed | 93 | 33 | 37 | 118 | 48 | 106105 | wrapper | |
| soCalled | 2 | 0 | 0 | 12 | 0 | 0 | <q> | |
| sourceDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| sp | 320117 | 12 | 1997 | 76237 | 42050 | 1661335 | structure | |
| spGrp | 0 | 0 | 0 | 0 | 35 | 0 | structure | |
| space | 0 | 1044 | 19559 | 0 | 20962 | 0 | editorial | |
| speaker | 304183 | 12 | 1978 | 76198 | 42021 | 1652394 | structure | |
| stage | 60645 | 39 | 17 | 10195 | 14041 | 246384 | structure | |
| subst | 0 | 0 | 11 | 0 | 0 | 2 | editorial | |
| supplied | 0 | 0 | 34 | 0 | 11095 | 0 | editorial | |
| surname | 0 | 490 | 38 | 0 | 0 | 0 | <name> | |
| table | 164693 | 7 | 103 | 19 | 5219 | 43935 | table | |
| tag | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| teiCorpus | 0 | 0 | 0 | 0 | 0 | 0 | structure | |
| teiHeader | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| term | 1451 | 113 | 181 | 51 | 0 | 0 | header | <seg> |
| text | 10171 | 126 | 50 | 645 | 848 | 69238 | structure | |
| textClass | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| textDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| time | 0 | 0 | 0 | 0 | 0 | 0 | interpretation | |
| title | 208735 | 6583 | 88 | 265 | 0 | 0 | structure | |
| titlePage | 0 | 1 | 48 | 359 | 1097 | 0 | titlepage | |
| titlePart | 0 | 1 | 85 | 467 | 2399 | 0 | titlepage | |
| titleStmt | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| trailer | 0 | 2 | 104 | 230 | 363 | 69313 | wrapper | |
| typeDesc | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| unclear | 0 | 1 | 117 | 2658 | 0 | 4038 | editorial | |
| val | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| value | 0 | 0 | 0 | 0 | 0 | 0 | header | |
| w | 0 | 0 | 0 | 0 | 0 | 0 | linguistic |
- castlist
- <actor> <castGroup> <castItem> <castList> <role> <roleDesc>
- character
- <g>
- editorial
- <abbr> <add> <addSpan/> <am> <choice> <corr> <del> <desc> <ex> <expan> <gap> <handShift/> <orig> <reg> <sic> <space> <subst> <supplied> <unclear>
- header
- <att> <biblFull> <biblScope> <biblStruct> <change> <charDecl> <charProp> <editor> <editorialDecl> <email> <encodingDesc> <extent> <fileDesc> <gi> <glyph> <glyphName> <idno> <imprint> <keywords> <licence> <listChange> <listPerson> <localName> <monogr> <msDesc> <msIdentifier> <person> <physDesc> <profileDesc> <publicationStmt> <relatedItem> <repository> <resp> <respStmt> <sourceDesc> <tag> <teiHeader> <term> <textClass> <textDesc> <titleStmt> <typeDesc> <val> <value>
- interpretation
- <author> <date> <foreign> <hi> <measure> <name> <num> <q> <quote> <ref> <rhyme> <rs> <seg> <time>
- linguistic
- <c> <pc> <s> <w>
- pictures
- <figDesc> <figure> <graphic>
- structure
- <ab> <address> <addrLine> <anchor/> <back> <bibl> <body> <cb/> <cit> <div> <floatingText> <formula> <front> <fw> <group> <head> <item> <l> <label> <lb/> <lg> <list> <listBibl> <milestone/> <note> <p> <pb/> <sp> <speaker> <spGrp> <stage> <TEI> <teiCorpus> <text> <title>
- table
- <cell> <row> <table>
- titlepage
- <docAuthor> <docDate> <docEdition> <docImprint> <docTitle> <imprimatur> <publisher> <pubPlace> <titlePage> <titlePart>
- wrapper
- <argument> <byline> <closer> <dateline> <epigraph> <opener> <postscript> <salute> <signed> <trailer>
6.6. The TEI infrastructure
| Module tei |
6.7. The header
The default set of elements for the header are loaded using the header module. In addition, elements from other modules are loaded, if they are tagged in the classification as being needed for the header only.
| Module header |
| Element <text> | change |
6.8. Transcription
In order to support the <sourcedoc> and <facsimile> elements, the basic transcriptional elements are loaded, and two attribute classes.
6.9. Attribute classes
| Class att.datcat | delete |
| Class att.declarable | delete |
| Class att.divLike | delete |
| Class att.global.linking | change |
| Class att.pointing | change |
| Class att.placement | change |
| Class att.dimensions | change |
| Class att.global.rendition | change |
6.10. Model classes
| Class model.entryPart | delete |
| Class model.placeNamePart | delete |
| Class model.placeStateLike | delete |
| Class model.egLike | delete |
| Class model.offsetLike | delete |
| Class model.pPart.msdesc | delete |
| Class model.oddDecl | delete |
| Class model.specDescLike | delete |
| Class model.entryPart | delete |
| Class model.placeNamePart | delete |
| Class model.placeStateLike | delete |
| Class model.certLike | delete |
| Class model.glossLike | delete |
6.11. Elements
The main part of Simple is the set of selected elements.
| Element <ab> | change |
| Element <abbr> | change |
| Element <actor> | change |
| Element <add> | change |
| Element <address> | change |
| Element <addrLine> | change |
| Element <addSpan/> | change |
| Element <am> | change |
| Element <anchor/> | change |
| Element <argument> | change |
| Element <author> | change |
| Element <back> | change |
| Element <bibl> | change |
| Element <body> | change |
| Element <byline> | change |
| Element <c> | change |
| Element <castGroup> | change |
| Element <castItem> | change |
| Element <castList> | change |
| Element <cb/> | change |
| Element <cell> | change |
| Element <choice> | change |
| Element <cit> | change |
| Element <closer> | change |
| Element <corr> | change |
| Element <date> | change |
| Element <dateline> | change |
| Element <del> | change |
| Element <desc> | change |
| Element <div> | change |
| Element <docAuthor> | change |
| Element <docDate> | change |
| Element <docEdition> | change |
| Element <docImprint> | change |
| Element <docTitle> | change |
| Element <epigraph> | change |
| Element <ex> | change |
| Element <expan> | change |
| Element <figDesc> | change |
| Element <figure> | change |
| Element <floatingText> | change |
| Element <foreign> | change |
| Element <formula> | change |
| Element <front> | change |
| Element <fw> | change |
| Element <g> | change |
| Element <gap> | change |
| Element <graphic> | change |
| Element <group> | change |
| Element <handShift/> | change |
| Element <head> | change |
| Element <hi> | change |
| Element <imprimatur> | change |
| Element <item> | change |
| Element <l> | change |
| Element <label> | change |
| Element <lb/> | change |
| Element <lg> | change |
| Element <list> | change |
| Element <listBibl> | change |
| Element <measure> | change |
| Element <milestone/> | change |
| Element <name> | change |
| Element <note> | change |
| Element <num> | change |
| Element <opener> | change |
| Element <orig> | change |
| Element <p> | change |
| Element <pb/> | change |
| Element <pc> | change |
| Element <postscript> | change |
| Element <publisher> | change |
| Element <pubPlace> | change |
| Element <q> | change |
| Element <quote> | change |
| Element <ref> | change |
| Element <reg> | change |
| Element <rhyme> | change |
| Element <role> | change |
| Element <roleDesc> | change |
| Element <row> | change |
| Element <rs> | change |
| Element <s> | change |
| Element <salute> | change |
| Element <seg> | change |
| Element <sic> | change |
| Element <signed> | change |
| Element <sp> | change |
| Element <space> | change |
| Element <speaker> | change |
| Element <spGrp> | change |
| Element <stage> | change |
| Element <subst> | change |
| Element <supplied> | change |
| Element <table> | change |
| Element <fileDesc> | change |
| Element <profileDesc> | change |
| Element <revisionDesc> | change |
| Element <encodingDesc> | change |
| Element <teiHeader> | change |
| Element <TEI> | change |
| Element <text> | change |
| Element <time> | change |
| Element <title> | change |
| Element <titlePage> | change |
| Element <titlePart> | change |
| Element <trailer> | change |
| Element <unclear> | change |
| Element <w> | change |